Real-time privacy protection method, device, equipment and system for Internet of Things traffic

By using homomorphic encryption algorithms and edge node aggregation processing in IoT traffic, the problems of communication bandwidth and security privacy protection in IoT applications are solved, and efficient and secure data transmission is achieved.

CN118694604BActive Publication Date: 2024-11-15HANGZHOU HIKVISION DIGITAL TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411153246.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-20
Publication Date
2024-11-15
Estimated Expiration
2044-08-20

AI Technical Summary

Technical Problem

There are challenges in IoT applications with communication bandwidth latency and security privacy protection, especially when processing multiple identical encrypted request messages, the prior art is difficult to effectively reduce communication bandwidth consumption and delay, and it is difficult to ensure data security.

Method used

The homomorphic encryption algorithm is used to encrypt the request messages of IoT devices, and determine similarity indicators in the edge nodes, aggregate similar encryption request messages, reduce the number of communications and computing resources, and at the same time, decrypt the private key of the centralized cloud server. and the public key encryption of edge nodes to achieve secure transmission of response data.

Benefits of technology

By aggregating encrypted request messages, communication bandwidth consumption and delay are reduced, computing resources are used, data transmission efficiency and security are improved, multiple encryption and decryption operations are avoided, and data decryption work is saved for edge nodes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118694604B_ABST
    Figure CN118694604B_ABST
Patent Text Reader

Abstract

The present application provides a method, device, equipment and system for real-time privacy protection of Internet of Things traffic, the method comprising: aggregating multiple similar encrypted request messages received within the maximum session time to obtain an aggregated encrypted request message; sending the aggregated encrypted request message and the identity corresponding to the aggregated encrypted request message to a cloud-based centralized server; upon receiving the first ciphertext response data sent by the cloud-based centralized server, decrypting the first ciphertext response data, and encrypting the response data based on the recorded identity of each Internet of Things device participating in the aggregation of the encrypted request message, using the public key of each Internet of Things device participating in the aggregation of the encrypted request message, obtaining second ciphertext response data, and sending the obtained second ciphertext response data to the corresponding Internet of Things devices. The method can reduce communication bandwidth consumption and delay while ensuring the security of Internet of Things traffic.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of information security technology, and in particular to a method, device, equipment and system for real-time privacy protection of Internet of Things traffic. Background Art

[0002] With the rapid development of Internet of Things (IoT) technology, IoT applications are widely integrated into all areas of social production and life. Although the IoT network paradigm is to achieve smart life by providing various services, IoT applications also face many challenges. The first challenge is related to the communication bandwidth that may cause latency issues, while the second challenge is related to ensuring the security and privacy of IoT applications. Summary of the invention

[0003] In view of this, the present application provides a method, device, equipment and system for real-time privacy protection of IoT traffic.

[0004] Specifically, the present application is implemented through the following technical solutions:

[0005] According to a first aspect of an embodiment of the present application, a real-time privacy protection method for Internet of Things traffic is provided, which is applied to an edge node, and the method includes:

[0006] Receive an encrypted request message and an identity identifier sent by an IoT device; wherein the encrypted request message is obtained by the IoT device by encrypting the request message using a homomorphic encryption algorithm based on the public key of the IoT device, and the request message is used to request a service of a specific IoT application;

[0007] For the encryption request messages received within the maximum session time, determine the similarity index of the encryption request messages, and determine the encryption request messages whose similarity index difference does not exceed a preset threshold as similar encryption request messages;

[0008] For multiple similar encryption request messages received within the maximum session time, the multiple similar encryption request messages are aggregated to obtain an aggregated encryption request message, and the identity identifier of each IoT device participating in the aggregation of the encryption request message is recorded; wherein the aggregated encryption request message is one of the multiple similar encryption request messages;

[0009] The aggregate encryption request message and the identity identifier corresponding to the aggregate encryption request message are sent to the cloud-based centralized server, and the cloud-based centralized server decrypts the aggregate encryption request message according to the identity identifier corresponding to the aggregate encryption request message using the private key of the IoT device to which the identity identifier belongs, to obtain a request message, and determines the corresponding response data according to the obtained request message, and encrypts the response data using the public key of the edge node to obtain first ciphertext response data;

[0010] When the first ciphertext response data sent by the cloud-based centralized server is received, the first ciphertext response data is decrypted according to the private key of the edge node to obtain the decrypted response data, and according to the recorded identity identifiers of each IoT device participating in the encryption request message aggregation, the response data is encrypted using the public key of each IoT device participating in the encryption request message aggregation to obtain second ciphertext response data with the same number of IoT devices participating in the encryption request message aggregation, and the obtained second ciphertext response data is sent to the corresponding IoT devices respectively, and the IoT device that receives the second ciphertext response data decrypts the second ciphertext response data using the private key of the IoT device to obtain the decrypted response data.

[0011] According to a second aspect of an embodiment of the present application, a real-time privacy protection device for Internet of Things traffic is provided, which is deployed on an edge node, and the device includes:

[0012] A communication unit, configured to receive an encrypted request message and an identity identifier sent by an IoT device; wherein the encrypted request message is obtained by the IoT device by encrypting the request message using a homomorphic encryption algorithm based on the public key of the IoT device, and the request message is used to request a service of a specific IoT application;

[0013] A determination unit, configured to determine, for the encryption request messages received within the maximum session time, a similarity index of the encryption request messages, and determine the encryption request messages whose similarity indexes differ by no more than a preset threshold as similar encryption request messages;

[0014] an aggregation unit, configured to aggregate multiple similar encryption request messages received within the maximum session time to obtain an aggregated encryption request message, and record the identity of each IoT device participating in the aggregation of the encryption request message; wherein the aggregated encryption request message is one of the multiple similar encryption request messages;

[0015] The communication unit is further configured to send the aggregate encryption request message and the identity identifier corresponding to the aggregate encryption request message to the cloud-based centralized server, and the cloud-based centralized server decrypts the aggregate encryption request message based on the identity identifier corresponding to the aggregate encryption request message using the private key of the IoT device to which the identity identifier belongs, to obtain a request message, and determines the corresponding response data based on the obtained request message, and encrypts the response data using the public key of the edge node to obtain first ciphertext response data;

[0016] The encryption and decryption unit is used to, when receiving the first ciphertext response data sent by the cloud centralized server, decrypt the first ciphertext response data according to the private key of the edge node to obtain the decrypted response data, and encrypt the response data according to the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity identifier of each IoT device participating in the encryption request message aggregation, to obtain the second ciphertext response data with the same number of copies as the number of IoT devices participating in the encryption request message aggregation;

[0017] The communication unit is also used to send the obtained second ciphertext response data to the corresponding Internet of Things devices respectively, and the Internet of Things devices that receive the second ciphertext response data use the private key of the Internet of Things device to decrypt the second ciphertext response data to obtain decrypted response data.

[0018] According to a third aspect of an embodiment of the present application, an electronic device is provided, wherein:

[0019] Memory, used to store computer programs;

[0020] The processor is used to implement the method provided in the first aspect when executing the program stored in the memory.

[0021] According to a fourth aspect of an embodiment of the present application, a computer program product is provided. The computer program product stores a computer program, and when the computer program is executed by a processor, the method provided in the first aspect is implemented.

[0022] According to a fifth aspect of an embodiment of the present application, a real-time privacy protection system for IoT traffic is provided, comprising: an IoT device, an edge node, and a cloud-based centralized server; wherein:

[0023] The IoT device is used to encrypt the request message using a homomorphic encryption algorithm based on the public key of the IoT device to obtain an encrypted request message, and send the encrypted request message and the identity of the device to the edge node; wherein the request message is used to request a service of a specific IoT application;

[0024] The edge node is used to receive the encryption request message and identity identifier sent by the IoT device; for the encryption request message received within the maximum session time, determine the similarity index of the encryption request message, and determine the encryption request message whose similarity index difference does not exceed a preset threshold as a similar encryption request message;

[0025] The edge node is further configured to aggregate multiple similar encryption request messages received within the maximum session time to obtain an aggregated encryption request message, and record the identity of each IoT device participating in the aggregation of the encryption request message; wherein the aggregated encryption request message is one of the multiple similar encryption request messages;

[0026] The edge node is further used to send the aggregate encryption request message and the identity identifier corresponding to the aggregate encryption request message to the cloud centralized server;

[0027] The cloud-based centralized server is used to decrypt the aggregated encrypted request message according to the identity identifier corresponding to the aggregated encrypted request message using the private key of the IoT device to which the identity identifier belongs to obtain a request message, determine the corresponding response data according to the obtained request message, encrypt the response data using the public key of the edge node to obtain first ciphertext response data, and send the first ciphertext response data to the edge node;

[0028] The edge node is further used to, upon receiving the first ciphertext response data sent by the cloud centralized server, decrypt the first ciphertext response data according to the private key of the edge node to obtain the decrypted response data, and encrypt the response data according to the recorded identity identifiers of the IoT devices participating in the encryption request message aggregation, respectively using the public keys of the IoT devices participating in the encryption request message aggregation, to obtain second ciphertext response data with the same number of copies as the number of IoT devices participating in the encryption request message aggregation, and send the obtained second ciphertext response data to the corresponding IoT devices respectively;

[0029] The edge node is further configured to, upon receiving the second ciphertext response data, decrypt the second ciphertext response data using the private key of the IoT device to obtain decrypted response data.

[0030] In the real-time privacy protection method for IoT traffic of the embodiment of the present application, when the edge node receives the encryption request message and identity identifier sent by the IoT device, for the encryption request message received within the maximum session time, the edge node can determine the similarity index of the encryption request message, and determine the encryption request message whose similarity index does not exceed the preset threshold as a similar encryption request message. For multiple similar encryption request messages received within the maximum session time, the multiple similar encryption request messages are aggregated to obtain an aggregated encryption request message, and the identity identifiers of each IoT device participating in the aggregation of the encryption request message are recorded. The edge node sends the aggregated encryption request message and the identity identifier corresponding to the aggregated encryption request message to the cloud-based centralized server, and the cloud-based centralized server decrypts the aggregated encryption request message using the private key of the IoT device to which the identity identifier belongs based on the identity identifier corresponding to the aggregated encryption request message to obtain a request message, and determines the corresponding response data based on the obtained request message, and encrypts the response data using the public key of the edge node to obtain first ciphertext response data. Then, when the first ciphertext response data sent by the cloud-based centralized server is received, the first ciphertext response data is decrypted based on the private key of the edge node. The encrypted data is encrypted to obtain the decrypted response data, and according to the recorded identity identifiers of each IoT device participating in the encryption request message aggregation, the public keys of each IoT device participating in the encryption request message aggregation are used to encrypt the response data to obtain the second ciphertext response data, the number of which is the same as the number of IoT devices participating in the encryption request message aggregation, and the obtained second ciphertext response data is sent to the corresponding IoT devices respectively, and the IoT device receiving the second ciphertext response data decrypts the second ciphertext response data using the private key of the IoT device to obtain the decrypted response data, and aggregates the encrypted request messages corresponding to the same request message, and aggregates multiple identical encrypted request messages into a single encrypted request message. For multiple identical encrypted request messages, a single encrypted request message is sent in the process of forwarding them to the cloud centralized server, and the cloud centralized server also returns a single response data, which reduces the communication bandwidth consumption and delay. Furthermore, since the cloud centralized server does not need to decrypt multiple identical encrypted request messages separately, it is not necessary to return multiple response data in the process of returning the response data, and encrypts the multiple response data separately, which reduces the number of encryption and decryption times and reduces the computing resource usage;In addition, since the IoT device uses a homomorphic encryption algorithm to encrypt the request message, the edge node does not need to decrypt the encrypted request message when calculating the similarity index. Instead, it can calculate the similarity index based on the encrypted request message and aggregate similar encrypted request messages based on the similarity index of the encrypted request message. Through the homomorphic encryption algorithm and the calculation of the similarity index of the encrypted data, the aggregation of encrypted data is achieved without decrypting the encrypted data, which reduces the workload of the edge node for data decryption and saves computing resources. ; BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A flowchart of a method for real-time privacy protection of Internet of Things traffic is shown as an exemplary embodiment of the present application;

[0032] Figure 2 This is a schematic diagram of an architecture of a specific application scenario shown in an exemplary embodiment of the present application;

[0033] Figure 3 A flowchart of a method for real-time privacy protection of Internet of Things traffic is shown as an exemplary embodiment of the present application;

[0034] Figure 4 This is a schematic diagram of the structure of a real-time privacy protection device for Internet of Things traffic shown as an exemplary embodiment of the present application;

[0035] Figure 5 This is a schematic diagram of the structure of another real-time privacy protection device for Internet of Things traffic, shown as another exemplary embodiment of the present application;

[0036] Figure 6 The figure is a schematic diagram of the hardware structure of an electronic device shown as an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0037] In order to enable those skilled in the art to better understand the technical solutions provided by the embodiments of the present application and to make the above-mentioned purposes, features and advantages of the embodiments of the present application more obvious and understandable, the technical solutions in the embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0038] See also Figure 1 , is a flow chart of a method for real-time privacy protection of IoT traffic provided by an embodiment of the present application, such as Figure 1 As shown, the real-time privacy protection method for IoT traffic may include the following steps:

[0039] Step S100, receiving an encrypted request message and an identity identifier sent by an IoT device; wherein the encrypted request message is obtained by the IoT device by encrypting the request message using a homomorphic encryption algorithm based on the public key of the IoT device, and the request message is used to request services of a specific IoT application.

[0040] In an embodiment of the present application, when an IoT device needs to request the service of a specific IoT application, a request message for requesting the service of the specific IoT application can be generated, and the request message can be encrypted using the public key of the IoT device and a homomorphic encryption algorithm to obtain an encrypted request message, and the encrypted request message and the identity of the IoT device can be sent to the edge node.

[0041] For example, homomorphic encryption is a special encryption technique that allows computation to be performed in an encrypted state without first decrypting the data.

[0042] Exemplarily, for any IoT device, its key pair (including a private key and a public key) can be generated and sent to the IoT device by the cloud-based centralized server during the process of the IoT device registering with the cloud-based centralized server (as a trusted institution).

[0043] Among them, since the private key of the IoT device cannot be known to other devices except the device itself and the centralized cloud server, and the request message encrypted with the public key requires the private key to decrypt, the request message encrypted by the IoT device using the public key cannot be decrypted by other devices except the device itself and the centralized cloud server, which effectively ensures the security of the request message.

[0044] Step S110: For the encryption request messages received within the maximum session time, determine the similarity index of the encryption request messages, and determine the encryption request messages whose similarity index difference does not exceed a preset threshold as similar encryption request messages.

[0045] In an embodiment of the present application, taking into account that in an actual scenario, there may be multiple IoT devices requesting the services of the same IoT application, the message contents in the request messages of the multiple IoT devices are the same, and the response data of the server in response to the multiple request messages are usually also the same. Therefore, in order to reduce communication bandwidth consumption and reduce latency, multiple identical request messages can be aggregated into a single request message and sent to the server.

[0046] Exemplarily, for request messages from different IoT devices requesting services from the same IoT application, the message contents are the same, but the message headers are different.

[0047] For example, suppose there are 10 IoT devices requesting services from the same IoT application. The edge node can aggregate the request messages from these 10 IoT devices into one request message. The edge node sends one request message to the server and obtains the server's response data to the request message.

[0048] It should be noted that, when the edge node obtains the response data corresponding to the request message, it can send it to the 10 IoT devices respectively.

[0049] In addition, since the IoT devices connected to the same edge node use a homomorphic encryption algorithm to encrypt request messages, when the message content of the request messages is the same, the results of specific operations on the encrypted request messages are usually similar.

[0050] Based on this, for the received encrypted request message, the edge node can calculate the similarity index based on the encrypted request message without decrypting the encrypted request message. Furthermore, the edge node can aggregate similar request messages without decrypting the encrypted request message.

[0051] Furthermore, in order to reduce the delay caused by request message aggregation, a maximum session time (such as 10ms, 20ms, etc.) can be set according to actual needs, and the request messages within the maximum session time can be aggregated.

[0052] Accordingly, in an embodiment of the present application, for an encrypted request message received within the maximum session time, the similarity index of the encrypted request message can be determined based on the encrypted request message without decrypting the encrypted request message, and encrypted request messages whose similarity index differs by no more than a preset threshold can be determined as similar encrypted request messages.

[0053] Exemplarily, when a homomorphic encryption algorithm is used to encrypt multiple request messages with the same message content, the difference between the similarity indicators corresponding to the multiple request messages does not exceed a preset threshold; when a homomorphic encryption algorithm is used to encrypt multiple request messages with different message contents, the difference between the similarity indicators corresponding to the multiple request messages will exceed the preset threshold.

[0054] In an example, determining the similarity index of the encrypted request message may include:

[0055] According to the encryption request message, a similarity index of the encryption request message is determined using a bilinear pairing algorithm of an elliptic curve.

[0056] Exemplarily, the similarity index of the encrypted request message may be determined using a bilinear pairing algorithm of an elliptic curve.

[0057] Exemplarily, for any encryption request message, the encryption request message can be used as an algorithm input and input into a bilinear pairing algorithm of an elliptic curve for operation, and the output result of the algorithm is used as a similarity index of the encryption request message.

[0058] Step S120: For multiple similar encryption request messages received within the maximum session time, aggregate the multiple similar encryption request messages to obtain an aggregated encryption request message, and record the identity of each IoT device participating in the encryption request message aggregation; wherein the aggregated encryption request message is one of the multiple similar encryption request messages.

[0059] In the embodiment of the present application, for multiple similar encryption request messages received within the maximum session time determined in the above manner, the multiple similar encryption request messages can be aggregated to obtain an aggregated encryption request message.

[0060] Exemplarily, the aggregated encrypted request message is one of the multiple similar encrypted request messages, that is, an encrypted request message can be selected from the multiple similar encrypted request messages as the aggregated encrypted request message.

[0061] In addition, in order to ensure that the response data returned by the server can be accurately sent to the corresponding IoT device, the edge node can also record the identity of each IoT device involved in the aggregation of encrypted request messages when aggregating multiple similar encrypted request messages. Then, in the subsequent process, when receiving the response data from the server, it can determine which IoT devices the response data needs to be sent to based on the recorded identity.

[0062] Step S130, the aggregate encryption request message and the identity identifier corresponding to the aggregate encryption request message are sent to the cloud-based centralized server, and the cloud-based centralized server decrypts the aggregate encryption request message based on the identity identifier corresponding to the aggregate encryption request message using the private key of the IoT device to which the identity identifier belongs, obtains the request message, determines the corresponding response data based on the obtained request message, encrypts the response data using the public key of the edge node, and obtains the first ciphertext response data.

[0063] In an embodiment of the present application, when an aggregated encryption request message is obtained by aggregating multiple similar encryption request messages, the edge node can send the aggregated encryption request message to a centralized server in the cloud.

[0064] Since the aggregate encryption request message is one of the encryption request messages among multiple similar encryption request messages (which can be called the target encryption request message), the edge node can determine the identity corresponding to the target encryption request message (that is, the identity of the IoT device that sends the target encryption request message) as the identity corresponding to the aggregate encryption request message, and send the identity together with the aggregate encryption request message to the cloud centralized server.

[0065] For example, assuming that the encryption request messages of device 1 to device 5 are similar encryption request messages, the aggregated encryption request message can be the encryption request message of any device from device 1 to device 5. Assuming that the aggregated encryption request message is the encryption request message of device 2 (i.e., the encryption request message sent by device 2 is the above-mentioned target encryption request message), when the aggregated encryption request message is sent to the cloud-based centralized server, the identity of device 2 (i.e., the identity corresponding to the aggregated encryption request message) can be sent to the cloud-based centralized server.

[0066] When the cloud-based centralized server receives an aggregate encryption request message sent by an edge node, it can determine the IoT device to which the identity identifier belongs based on the identity identifier corresponding to the aggregate encryption request message, and use the recorded private key of the IoT device to decrypt the aggregate encryption request message.

[0067] For example, any IoT device can be registered with a cloud-based centralized server. During the registration process, the cloud-based centralized server can generate a key pair (including a private key and a public key) for the IoT device, send the generated key pair to the IoT device, and record the corresponding relationship between the IoT device's identity and the key pair.

[0068] The cloud-based centralized server can determine the corresponding response data based on the decrypted request message, and encrypt the response data using the public key of the edge node to obtain the corresponding ciphertext response message (which can be called the first ciphertext response message), and send the first ciphertext response message to the edge node.

[0069] Exemplarily, any edge node can be registered with a cloud-based centralized server. During the registration process, the cloud-based centralized server can generate a key pair (including a private key and a public key) for the edge node, send the generated key pair to the edge node, and record the corresponding relationship between the edge node's identity and the key pair.

[0070] Step S140: When receiving the first ciphertext response data sent by the cloud centralized server, the first ciphertext response data is decrypted according to the private key of the edge node to obtain the decrypted response data, and according to the recorded identity identifiers of each IoT device participating in the encryption request message aggregation, the response data is encrypted using the public key of each IoT device participating in the encryption request message aggregation to obtain second ciphertext response data with the same number of copies as the number of IoT devices participating in the encryption request message aggregation, and the obtained second ciphertext response data is sent to the corresponding IoT devices respectively, and the IoT device that receives the second ciphertext response data decrypts the second ciphertext response data using the private key of the IoT device to obtain the decrypted response data.

[0071] In an embodiment of the present application, when the edge node receives the first encrypted response data sent by the cloud-based centralized server, it can decrypt the first encrypted response data according to the private key of the edge node to obtain the decrypted response data.

[0072] The edge node can encrypt the response data based on the recorded identity identifiers of each IoT device participating in the encryption request message aggregation, using the public keys of each IoT device participating in the encryption request message aggregation to obtain corresponding ciphertext response data (which can be called second ciphertext response data).

[0073] Exemplarily, the number of copies of the second ciphertext response data is consistent with the number of IoT devices participating in the encryption request message aggregation.

[0074] For example, assuming that the IoT devices participating in the encryption request message aggregation include devices 1 to 5, for the decrypted response data, the response data can be encrypted using the public key of device 1 to obtain a second ciphertext response data; the response data can be encrypted using the public key of device 2 to obtain a second ciphertext response data; ...; the response data can be encrypted using the public key of device 5 to obtain a second ciphertext response data.

[0075] Exemplarily, the public key of the IoT device can be sent by the cloud-based centralized server to the edge node. For example, the cloud-based centralized server can send the public key of the IoT device connected to the edge node to the edge node, which will be stored by the edge node. Alternatively, the public key of the IoT device can be sent to the edge node when the IoT device sends an encryption request message to the edge node, and the edge node will cache it. When the encryption of the second ciphertext response data is completed, the edge node can delete the public key of the IoT device to reduce the consumption of storage resources.

[0076] The edge node can send the obtained second ciphertext response data to the corresponding IoT devices respectively.

[0077] For example, the second ciphertext response data encrypted using the public key of device 1 is sent to device 1, the second ciphertext response data encrypted using the public key of device 2 is sent to device 2, ..., the second ciphertext response data encrypted using the public key of device 5 is sent to device 5.

[0078] When the IoT device receives the second ciphertext response data, it can use the private key of the IoT device to decrypt the second ciphertext response data to obtain the decrypted response data.

[0079] It can be seen that in Figure 1In the method flow shown, when the edge node receives the encryption request message and identity identifier sent by the IoT device, for the encryption request message received within the maximum session time, the edge node can determine the similarity index of the encryption request message, and determine the encryption request message whose similarity index does not exceed the preset threshold as a similar encryption request message. For multiple similar encryption request messages received within the maximum session time, the multiple similar encryption request messages are aggregated to obtain an aggregated encryption request message, and the identity identifiers of each IoT device participating in the aggregation of the encryption request message are recorded. The edge node sends the aggregated encryption request message and the identity identifier corresponding to the aggregated encryption request message to the cloud-based centralized server, and the cloud-based centralized server decrypts the aggregated encryption request message based on the identity identifier corresponding to the aggregated encryption request message and the private key of the IoT device to which the identity identifier belongs to obtain a request message, and determines the corresponding response data based on the obtained request message, and encrypts the response data using the public key of the edge node to obtain first ciphertext response data. Then, when the first ciphertext response data sent by the cloud-based centralized server is received, the first ciphertext response data is decrypted based on the private key of the edge node to obtain the decrypted data. The response data is obtained, and according to the recorded identity identifiers of each IoT device participating in the encryption request message aggregation, the response data is encrypted using the public keys of each IoT device participating in the encryption request message aggregation, and the second ciphertext response data is obtained, the number of copies of which is consistent with the number of IoT devices participating in the encryption request message aggregation, and the obtained second ciphertext response data is sent to the corresponding IoT devices respectively, and the IoT device that receives the second ciphertext response data decrypts the second ciphertext response data using the private key of the IoT device to obtain the decrypted response data, and the encrypted request messages corresponding to the same request message are aggregated, and multiple identical encrypted request messages are aggregated into a single encrypted request message. For multiple identical encrypted request messages, a single encrypted request message is sent in the process of forwarding to the cloud centralized server, and the cloud centralized server also returns a single response data, which reduces the communication bandwidth consumption and delay. Furthermore, since the cloud centralized server does not need to decrypt multiple identical encrypted request messages separately, it is not necessary to return multiple response data in the process of returning the response data, and encrypt the multiple response data separately, which reduces the number of encryption and decryption times and reduces the computing resource usage;In addition, since the IoT device uses a homomorphic encryption algorithm to encrypt the request message, the edge node does not need to decrypt the encrypted request message when calculating the similarity index. Instead, it can calculate the similarity index based on the encrypted request message and aggregate similar encrypted request messages based on the similarity index of the encrypted request message. Through the homomorphic encryption algorithm and the calculation of the similarity index of the encrypted data, the aggregation of encrypted data is achieved without decrypting the encrypted data, which reduces the workload of the edge node for data decryption and saves computing resources. ;

[0080] In some embodiments, the identity of the IoT device is a pseudo identity;

[0081] The pseudo identity of the IoT device is generated by the cloud-based centralized server based on the real identity of the IoT and a random salt number during the registration process of the IoT device with the cloud-based centralized server.

[0082] For example, in order to protect the real identity of the IoT device, during the registration process of the IoT device with the cloud-based centralized server, the cloud-based centralized server can generate a pseudo-identity for it (which can be represented by a pseudo-identity identifier).

[0083] In order to improve the security of the pseudo-identity of IoT devices, the pseudo-identity generated by the cloud centralized server for the IoT device can be a pseudo-identity with a random salt value to protect the pseudo-identity of the IoT device from rainbow table attacks.

[0084] For example, a centralized cloud server can combine the real identity of an IoT device with a random salt value and use a hash function to calculate a pseudo-identity.

[0085] Based on the pseudo-identity, the IoT device uses the pseudo-identity as an identity during a service request.

[0086] Exemplarily, when the edge node receives the encrypted request message and the pseudo-identity sent by the IoT device, the pseudo-identity of the IoT device can be verified.

[0087] For example, the edge node can query whether the received pseudo-identity (which can be called the matched target pseudo-identity) exists in the pseudo-identity list of IoT devices maintained locally. If it exists, it is determined that the pseudo-identity verification of the IoT device has passed (i.e., the identity authentication has passed), and the IoT device is determined to be a registered IoT device. If it does not exist, it is determined that the pseudo-identity verification of the IoT device has failed (i.e., the identity authentication has failed), and the IoT device is determined to be an unregistered IoT device.

[0088] Exemplarily, for an IoT device that has passed identity authentication, similarity index calculation and subsequent processing can be performed on the encrypted request message sent by the IoT device. The specific processing method can refer to the description related to steps S110~S140 in the above method flow.

[0089] Exemplarily, for an encryption request message sent by an IoT device that fails identity authentication, a response to the encryption request message can be refused, that is, no subsequent processing is required (that is, the encryption request message will not trigger the processing of steps S110~S140). For example, the encryption request message sent by an IoT device that fails identity authentication can be discarded.

[0090] Exemplarily, the pseudo-identity of the IoT device can be sent by the cloud-based centralized server to the edge node to which the IoT device is connected, and the edge node can maintain a pseudo-identity list based on the pseudo-identity of the IoT device sent by the cloud-based centralized server.

[0091] In some embodiments, based on the recorded identity identifiers of each IoT device participating in the encryption request message aggregation, using the public key of each IoT device participating in the encryption request message aggregation respectively, before encrypting the response data, the following may also be included:

[0092] Receive the public key sent by each IoT device, associate the identity of each IoT device, and cache the public key of each IoT device;

[0093] The above-mentioned encrypting the response data using the public key of each IoT device participating in the encryption request message aggregation based on the recorded identity of each IoT device participating in the encryption request message aggregation may include:

[0094] For any IoT device participating in encryption request message aggregation, query the cached public key of the IoT device based on the identity of the IoT device;

[0095] Encrypt the response data using the public key of the IoT device;

[0096] The above-mentioned method further includes: after encrypting the response data based on the recorded identity identifiers of each IoT device participating in the encryption request message aggregation, using the public keys of each IoT device participating in the encryption request message aggregation respectively;

[0097] Delete the cached public keys of each IoT device that participates in the encryption request message aggregation.

[0098] Exemplarily, the public key of the IoT device may be sent by the IoT device to the edge node.

[0099] For example, when an IoT device sends an encryption request message and an identity identifier to an edge node, it can also send a public key to the edge node.

[0100] Edge nodes can associate the identity of IoT devices and cache the public keys of IoT devices.

[0101] Correspondingly, when receiving the first ciphertext response data sent by the cloud-based centralized server, the edge node can decrypt the first ciphertext response data based on the private key of the edge node to obtain the decrypted response data, and based on the recorded identity identifiers of each IoT device participating in the encryption request message aggregation, query the cached public keys of each IoT device participating in the encryption request message aggregation, and use the public keys of each IoT device participating in the encryption request message aggregation to encrypt the response data, and obtain the second ciphertext response data, the number of which is consistent with the number of IoT devices participating in the encryption request message aggregation.

[0102] Exemplarily, when the edge node completes encryption of the second ciphertext response data, it may delete the cached public keys of each IoT device that participates in the encryption request message aggregation.

[0103] It can be seen that in this embodiment, the edge node does not need to store the public key of the IoT device all the time, which can save the storage resources of the edge node.

[0104] In other embodiments, the above-mentioned encrypting the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation may include:

[0105] Obtaining the identity of each IoT device participating in the encryption request message aggregation from the cloud center server based on the recorded identity of each IoT device participating in the encryption request message aggregation;

[0106] The response data is encrypted using the public key of each IoT device that participates in the encryption request message aggregation.

[0107] Exemplarily, the edge node can obtain the identity identifiers of each IoT device participating in the encryption request message aggregation from the cloud center server based on the recorded identity identifiers of each IoT device participating in the encryption request message aggregation.

[0108] For example, the edge node can send a public key acquisition request carrying the identity identifiers of each IoT device participating in the encryption request message aggregation to the cloud centralized server.

[0109] When the cloud-based centralized server receives the public key acquisition request, it can send the corresponding public key to the edge node based on the identity of the IoT device carried in the public key acquisition request.

[0110] For the decrypted response data obtained in the above manner, the edge node can use the public key of each IoT device participating in the encryption request message aggregation to encrypt the response data, and obtain the second ciphertext response data with the same number of copies as the number of IoT devices participating in the encryption request message aggregation.

[0111] Exemplarily, when the edge node completes the encryption of the second ciphertext response data, it is not necessary to save the public keys of each IoT device that participates in the encryption request message aggregation.

[0112] It can be seen that in this embodiment, the edge node can obtain the public key of the IoT device from the cloud centralized server when necessary, without having to keep the public key of the IoT device all the time, which can save the storage resources of the edge node.

[0113] In some other embodiments, before encrypting the response data based on the recorded identity identifiers of the IoT devices participating in the encryption request message aggregation, using the public keys of the IoT devices participating in the encryption request message aggregation, the following further comprises:

[0114] Receive the identity and public key of the IoT device sent by the cloud centralized server, associate the identity of the IoT device, and save the public key of the IoT device;

[0115] The above-mentioned encrypting the response data using the public key of each IoT device participating in the encryption request message aggregation based on the recorded identity of each IoT device participating in the encryption request message aggregation may include:

[0116] For any IoT device that participates in the encryption request message aggregation, query the stored public key of the IoT device based on the identity of the IoT device;

[0117] The response data is encrypted using the public key of the IoT device.

[0118] Exemplarily, the identity and public key of the IoT device can be sent from a cloud-based centralized server to an edge node and stored by the edge node.

[0119] For example, for any IoT device, during the process of registering the IoT device with a cloud-based centralized server, after determining the identity and public key of the IoT device, the cloud-based centralized server can send the identity and public key of the IoT device to the edge node to which the IoT device is connected.

[0120] When the edge node receives the identity and public key of the IoT device sent by the cloud centralized server, it can associate the identity of the IoT device and save the public key of the IoT device.

[0121] Accordingly, when the edge node obtains the decrypted response data in the above manner, it can query the stored public keys of each IoT device participating in the encryption request message aggregation based on the recorded identity identifiers of each IoT device participating in the encryption request message aggregation, and use the public keys of each IoT device participating in the encryption request message aggregation to encrypt the response data, thereby obtaining a second ciphertext response data whose number is consistent with the number of IoT devices participating in the encryption request message aggregation.

[0122] It can be seen that the edge node can pre-save the public key of the IoT device. When the public key of the IoT device is needed to encrypt the second ciphertext response data, the saved public key of the IoT device can be read. There is no need to obtain the public key of the same IoT device through communication interactions multiple times, which can improve the efficiency of encrypting the second ciphertext response data.

[0123] In order to enable those skilled in the art to better understand the technical solutions provided by the embodiments of the present application, the technical solutions provided by the embodiments of the present application are described below in conjunction with specific application scenarios.

[0124] See also Figure 2 , is a schematic diagram of an architecture of a specific application scenario provided by an embodiment of the present application, such as Figure 2 As shown, IoT devices access the network through edge nodes and can request services from IoT applications after completing registration with the centralized server in the cloud.

[0125] As a trusted structure, the centralized server in the cloud accepts registrations of IoT devices and edge nodes, assigns pseudo-avatar identities to IoT devices and edge nodes, and generates key pairs (including public and private keys).

[0126] based on Figure 2 In the application scenario shown, the implementation process of the real-time privacy protection method for IoT traffic provided by the embodiment of the present application can be as follows:

[0127] 1. Device Registration

[0128] 1.1. Edge Node Registration

[0129] For example, an edge node joins the system (e.g. Figure 2 When the network is established (as shown in the figure), you can register with the centralized server in the cloud.

[0130] During the registration process, if the cloud-based centralized server passes the real identity authentication of the edge node, it can assign a pseudo-identity to the edge node, generate a key pair, and record the pseudo-identity and key pair of the edge node.

[0131] Exemplarily, the registration request of the edge node may include the real identity of the edge node, and the cloud-based centralized server may calculate the corresponding pseudo identity based on the real identity of the edge node and a random salt value using a hash algorithm.

[0132] Exemplarily, for an edge node, the cloud-based centralized server can select a random number as a private key for the edge node, and calculate the corresponding public key based on the private key.

[0133] For example, the corresponding public key can be calculated based on the private key and the generator.

[0134] Among them, the generator can be determined by the cloud-based centralized server during the system initialization phase.

[0135] Exemplarily, for an edge node that has successfully registered, the cloud-based centralized server can send the generated pseudo-identity and key pair to the edge node through a secure channel.

[0136] The edge node can securely store its pseudo-identity and key pair, for example, in secure hardware, for subsequent communication and authentication in the network.

[0137] 1.2. IoT device registration

[0138] For example, an IoT device joins the system (e.g. Figure 2 When the network is established (as shown in the figure), you can register with the centralized server in the cloud.

[0139] During the registration process, if the cloud-based centralized server passes the real identity authentication of the IoT device, it can assign a pseudo-identity to the IoT device, generate a key pair, and record the pseudo-identity and key pair of the IoT device.

[0140] Exemplarily, the registration request of the IoT device may include the real identity of the IoT device, and the cloud-based centralized server may calculate the corresponding pseudo identity based on the real identity of the IoT device and a random salt value using a hash algorithm.

[0141] Exemplarily, for an IoT device, the cloud-based centralized server can select a random number as a private key for the IoT device, and calculate the corresponding public key based on the private key.

[0142] For example, the corresponding public key can be calculated based on the private key and the generator.

[0143] Among them, the generator can be determined by the cloud-based centralized server during the system initialization phase.

[0144] Exemplarily, for an IoT device that has been successfully registered, the cloud-based centralized server can send the generated pseudo-identity and key pair to the IoT device through a secure channel.

[0145] In addition, the cloud-based centralized server can also send the pseudo-identity identifier of the successfully registered IoT device to the edge node to which the IoT device is connected, and the edge node maintains a list of pseudo-identity identifiers of the successfully registered IoT devices connected to this node.

[0146] IoT devices can store their pseudo-identities and key pairs securely, for example, in secure hardware, for subsequent communication and authentication in the network.

[0147] 2. Service Request

[0148] Exemplarily, for any IoT device, if the registration is successful, the service of the IoT application can be requested.

[0149] For example, when an IoT device needs to request services from an IoT application, it can generate a request message, use the public key of the device, and encrypt the request message using a homomorphic encryption algorithm to obtain an encrypted request message, and then send the encrypted request message and the pseudo-identity of the device to the edge node.

[0150] In one example, the IoT device may use the public key of the device to encrypt the pseudo-identity of the device, and send the encrypted pseudo-identity together with the encryption request message to the edge node.

[0151] 3. Request message aggregation

[0152] When the edge node receives the encrypted request message and pseudo identity sent by the IoT device, it can authenticate the IoT device.

[0153] Exemplarily, the edge node may query a pseudo-identity list maintained by the node based on the received pseudo-identity to determine whether there is a matching target pseudo-identity.

[0154] When the target pseudo-identity is found, it can be determined that the identity authentication of the IoT device has been passed;

[0155] When the target pseudo-identity is not found, it can be determined that the identity authentication of the IoT device has failed.

[0156] It should be noted that, when the pseudo-identity sent by the IoT device is an encrypted pseudo-identity, for any IoT device that has sent an encryption request message, the edge node can encrypt each pseudo-identity in the pseudo-identity list based on the public key of the IoT device, and query whether there is a target encrypted pseudo-identity that matches the received encrypted pseudo-identity.

[0157] The encryption algorithm used by the edge node to encrypt the pseudo-identity is the same as the encryption algorithm used by the IoT device to encrypt the pseudo-identity.

[0158] For encryption request messages received within the maximum session time and sent by IoT devices that have passed identity authentication, the edge node can use the bilinear pairing algorithm of the elliptic curve to determine the similarity index of the encryption request messages, and determine the encryption request messages whose similarity index difference (absolute value of the difference) does not exceed a preset threshold as similar encryption request messages.

[0159] Exemplarily, among multiple similar encrypted request messages, the difference between similarity indicators of any two encrypted request messages does not exceed a preset threshold.

[0160] For multiple similar encryption request messages within the maximum session time, the edge node can aggregate the multiple similar encryption request messages to obtain an aggregated encryption request message, and record the identity of each IoT device participating in the encryption request message aggregation.

[0161] Exemplarily, the aggregated encryption request message is one of the encryption request messages among the multiple similar encryption request messages.

[0162] The edge node can send the aggregated encryption request message, the pseudo-identity identifier corresponding to the aggregated encryption request message, and the pseudo-identity identifier of the node to the cloud centralized server.

[0163] 4. Server Response

[0164] Exemplarily, when the cloud-based centralized server receives an aggregated encryption request message sent by an edge node, a pseudo-identity identifier corresponding to the aggregated encryption request message, and the pseudo-identity identifier of the edge node, it can authenticate the edge node based on the pseudo-identity identifier of the edge node to determine whether the edge node is a registered edge node.

[0165] For example, the cloud-based centralized server can query the maintained pseudo-identity list of edge nodes (the pseudo-identity list is used to record the pseudo-identities of registered edge nodes) based on the pseudo-identity of the edge node to determine whether there is a matching target pseudo-identity; if there is a matching target pseudo-identity, it is determined that the edge node identity authentication has passed; if there is no matching target pseudo-identity, it is determined that the edge node identity authentication has failed.

[0166] When the edge node identity authentication is passed, the cloud-based centralized server determines the IoT device to which the pseudo-identity belongs based on the pseudo-identity corresponding to the aggregated encrypted request message, and uses the private key of the IoT device to decrypt the aggregated encrypted request message to obtain a plaintext request message, and determines the corresponding response data based on the obtained request message.

[0167] The cloud-based centralized server encrypts the response data using the public key of the edge node to obtain ciphertext response data (i.e., the first ciphertext response data mentioned above), and sends the first ciphertext response data and the pseudo-identity corresponding to the aggregated encryption request message to the edge node.

[0168] 5. Edge Node Response

[0169] Exemplarily, when the edge node receives the first ciphertext response data and the pseudo-identity corresponding to the aggregate encryption request message, the edge node uses the private key of the node to decrypt the first ciphertext response data to obtain the plaintext response data.

[0170] The edge node queries the identity of each IoT device participating in the aggregation of the encryption request message based on the pseudo-identity corresponding to the aggregated encryption request message, and uses the public key of each IoT device participating in the aggregation of the encryption request message to encrypt the plaintext response data, obtains the corresponding ciphertext response data (i.e., the above-mentioned second ciphertext response data), and sends the obtained second ciphertext response data to the corresponding IoT devices respectively.

[0171] Exemplarily, for any IoT device participating in encryption request message aggregation, the second ciphertext response data sent to the IoT device is encrypted using the public key of the IoT device.

[0172] 6. IoT devices obtain response data

[0173] Exemplarily, when the IoT device receives the second ciphertext response data sent by the edge node, the IoT device uses the private key of the device to decrypt the second ciphertext response data to obtain plaintext response data.

[0174] For an example, the flowchart of the method for implementing the real-time privacy protection of IoT traffic can be found in Figure 3 .

[0175] The method provided by the present application is described above. The device provided by the present application is described below:

[0176] See also Figure 4 , is a schematic diagram of the structure of a real-time privacy protection device for IoT traffic provided by an embodiment of the present application, wherein the device can be deployed at the edge node in the above embodiment, such as Figure 4 As shown, the real-time privacy protection device for IoT traffic may include:

[0177] The communication unit 410 is used to receive an encrypted request message and an identity identifier sent by an IoT device; wherein the encrypted request message is obtained by the IoT device by encrypting the request message using a homomorphic encryption algorithm based on the public key of the IoT device, and the request message is used to request a service of a specific IoT application;

[0178] A determination unit 420 is configured to determine a similarity index of the encryption request messages received within the maximum session time, and determine encryption request messages whose similarity indexes differ by no more than a preset threshold as similar encryption request messages;

[0179] The aggregation unit 430 is used to aggregate multiple similar encryption request messages received within the maximum session time to obtain an aggregated encryption request message, and record the identity of each IoT device participating in the aggregation of the encryption request message; wherein the aggregated encryption request message is one of the multiple similar encryption request messages;

[0180] The communication unit 410 is further used to send the aggregate encryption request message and the identity identifier corresponding to the aggregate encryption request message to the cloud-based centralized server, and the cloud-based centralized server decrypts the aggregate encryption request message according to the identity identifier corresponding to the aggregate encryption request message using the private key of the IoT device to which the identity identifier belongs to obtain a request message, and determines the corresponding response data according to the obtained request message, and encrypts the response data using the public key of the edge node to obtain first ciphertext response data;

[0181] The encryption and decryption unit 440 is used to, when receiving the first ciphertext response data sent by the cloud centralized server, decrypt the first ciphertext response data according to the private key of the edge node to obtain the decrypted response data, and encrypt the response data according to the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity identifier of each IoT device participating in the encryption request message aggregation, to obtain the second ciphertext response data with the same number of copies as the number of IoT devices participating in the encryption request message aggregation;

[0182] The communication unit 410 is also used to send the obtained second ciphertext response data to the corresponding Internet of Things devices respectively, and the Internet of Things devices that receive the second ciphertext response data use the private key of the Internet of Things device to decrypt the second ciphertext response data to obtain decrypted response data.

[0183] In some embodiments, the identity of the IoT device is a pseudo identity;

[0184] The pseudo identity of the IoT device is generated by the cloud-based centralized server according to the real identity of the IoT and a random salt number during the registration of the IoT device with the cloud-based centralized server.

[0185] In some embodiments, the identity identifier of the IoT device is a pseudo identity identifier assigned to the IoT device by the cloud-based centralized server during the registration process of the IoT device with the cloud-based centralized server;

[0186] like Figure 5 As shown, the real-time privacy protection device for IoT traffic also includes:

[0187] The identity authentication unit 450 is used to query the maintained pseudo-identity list of the Internet of Things devices according to the pseudo-identity sent by the Internet of Things device for the encrypted request message and identity sent by any Internet of Things device, and determine whether there is a matching target pseudo-identity; wherein the pseudo-identity list of the Internet of Things device includes the pseudo-identity of the Internet of Things device registered with the cloud-based centralized server; the pseudo-identity of the Internet of Things device is sent by the cloud-based centralized server to the edge node to which the Internet of Things device is connected, and the pseudo-identity list of the Internet of Things device is maintained by the edge node according to the pseudo-identity of the Internet of Things device sent by the cloud-based centralized server; if there is a matching target pseudo-identity, it is determined that the identity authentication of the Internet of Things device is passed; wherein the encrypted request message sent by the Internet of Things device that has passed the identity authentication participates in the calculation and subsequent processing of the similarity index; if there is no matching target pseudo-identity, it is determined that the identity authentication of the Internet of Things device is not passed, and the encrypted request message sent by the Internet of Things device that has failed the identity authentication is refused to be responded.

[0188] In some embodiments, the determining unit 420 determines the similarity index of the encrypted request message, including:

[0189] According to the encryption request message, a similarity index of the encryption request message is determined using a bilinear pairing algorithm of an elliptic curve.

[0190] In some embodiments, the communication unit 410 is further used to receive a public key sent by each IoT device;

[0191] The encryption and decryption unit 440 is also used to associate the identity of each IoT device and cache the public key of each IoT device;

[0192] The encryption / decryption unit 440 encrypts the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation, including:

[0193] For any IoT device participating in encryption request message aggregation, query the cached public key of the IoT device based on the identity of the IoT device;

[0194] Encrypt the response data using the public key of the IoT device;

[0195] The encryption / decryption unit 440 encrypts the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation, and further includes:

[0196] Delete the cached public keys of each IoT device that participates in the encryption request message aggregation;

[0197] or,

[0198] The encryption / decryption unit 440 encrypts the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation, including:

[0199] Obtaining the identity identifiers of the various IoT devices participating in the encryption request message aggregation from the cloud center server according to the recorded identity identifiers of the various IoT devices participating in the encryption request message aggregation;

[0200] The response data is encrypted using the public key of each IoT device participating in the encryption request message aggregation;

[0201] or,

[0202] The communication unit 410 is also used to receive the identity and public key of the IoT device sent by the cloud centralized server;

[0203] The encryption and decryption unit 440 is also used to associate the identity of the IoT device and store the public key of the IoT device;

[0204] The encryption / decryption unit 440 encrypts the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation, including:

[0205] For any IoT device that participates in the encryption request message aggregation, query the stored public key of the IoT device based on the identity of the IoT device;

[0206] The response data is encrypted using the public key of the IoT device.

[0207] An embodiment of the present application also provides an electronic device, including a processor and a memory, wherein the memory is used to store computer programs; the processor is used to implement the real-time privacy protection method for IoT traffic described above when executing the program stored in the memory.

[0208] See also Figure 6 , is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. The electronic device may include a processor 601 and a memory 602 storing machine executable instructions. The processor 601 and the memory 602 may communicate via a system bus 603. In addition, by reading and executing the machine executable instructions corresponding to the real-time privacy protection logic of IoT traffic in the memory 602, the processor 601 may execute the real-time privacy protection method for IoT traffic described above.

[0209] The memory 602 mentioned herein may be any electronic, magnetic, optical or other physical storage device that may contain or store information, such as executable instructions, data, etc. For example, the machine-readable storage medium may be: RAM (RadomAccess Memory, random access memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state drive, any type of storage disk (such as optical disk, DVD, etc.), or similar storage medium, or a combination thereof.

[0210] In some embodiments, a machine-readable storage medium is also provided. Figure 6 The memory 602 in the machine-readable storage medium stores machine executable instructions, and when the machine executable instructions are executed by the processor, the real-time privacy protection method for IoT traffic described above is implemented. For example, the machine-readable storage medium can be ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

[0211] An embodiment of the present application also provides a computer program product, which stores a computer program, and when a processor executes the computer program, it prompts the processor to execute the real-time privacy protection method for Internet of Things traffic described above.

[0212] The embodiment of the present application also provides a real-time privacy protection system for IoT traffic, including: an IoT device, an edge node, and a cloud-based centralized server; wherein:

[0213] The IoT device is used to encrypt the request message using a homomorphic encryption algorithm based on the public key of the IoT device to obtain an encrypted request message, and send the encrypted request message and the identity of the device to the edge node; wherein the request message is used to request a service of a specific IoT application;

[0214] The edge node is used to receive the encryption request message and identity identifier sent by the IoT device; for the encryption request message received within the maximum session time, determine the similarity index of the encryption request message, and determine the encryption request message whose similarity index difference does not exceed a preset threshold as a similar encryption request message;

[0215] The edge node is further configured to aggregate multiple similar encryption request messages received within the maximum session time to obtain an aggregated encryption request message, and record the identity of each IoT device participating in the aggregation of the encryption request message; wherein the aggregated encryption request message is one of the multiple similar encryption request messages;

[0216] The edge node is further used to send the aggregate encryption request message and the identity identifier corresponding to the aggregate encryption request message to the cloud centralized server;

[0217] The cloud-based centralized server is used to decrypt the aggregated encrypted request message according to the identity identifier corresponding to the aggregated encrypted request message using the private key of the IoT device to which the identity identifier belongs to obtain a request message, determine the corresponding response data according to the obtained request message, encrypt the response data using the public key of the edge node to obtain first ciphertext response data, and send the first ciphertext response data to the edge node;

[0218] The edge node is further used to, upon receiving the first ciphertext response data sent by the cloud centralized server, decrypt the first ciphertext response data according to the private key of the edge node to obtain the decrypted response data, and encrypt the response data according to the recorded identity identifiers of the IoT devices participating in the encryption request message aggregation, respectively using the public keys of the IoT devices participating in the encryption request message aggregation, to obtain second ciphertext response data with the same number of copies as the number of IoT devices participating in the encryption request message aggregation, and send the obtained second ciphertext response data to the corresponding IoT devices respectively;

[0219] The edge node is further configured to, upon receiving the second ciphertext response data, decrypt the second ciphertext response data using the private key of the IoT device to obtain decrypted response data.

[0220] In some embodiments, the identity identifier of the IoT device is a pseudo identity identifier assigned to the IoT device by the cloud-based centralized server during the registration process of the IoT device with the cloud-based centralized server;

[0221] The edge node is also used to query the maintained pseudo-identity list of IoT devices for the encrypted request message and identity sent by any IoT device, based on the pseudo-identity sent by the IoT device, to determine whether there is a matching target pseudo-identity; wherein the pseudo-identity list of IoT devices includes the pseudo-identities of IoT devices registered with the cloud-based centralized server; if there is a matching target pseudo-identity, determine that the identity authentication of the IoT device is passed; if there is no matching target pseudo-identity, determine that the identity authentication of the IoT device is failed.

[0222] In some embodiments, the edge node is specifically used to send the aggregate encryption request message, the identity corresponding to the aggregate encryption request message, and the pseudo identity of the node to the cloud centralized server; wherein the pseudo identity of the edge node is allocated to the edge node by the cloud centralized server during the registration process of the edge node;

[0223] The cloud-based centralized server is further used to authenticate the edge node based on the pseudo-identity identifier of the edge node;

[0224] The cloud-based centralized server is specifically used to, when the edge node identity authentication is passed, decrypt the aggregated encrypted request message based on the identity identifier corresponding to the aggregated encrypted request message and the private key of the Internet of Things device to which the identity identifier belongs, to obtain a request message, and determine the corresponding response data based on the obtained request message, encrypt the response data using the public key of the edge node, to obtain first ciphertext response data, and send the first ciphertext response data to the edge node.

[0225] Exemplarily, IoT devices, edge nodes, and cloud-based centralized servers can implement real-time privacy protection of IoT traffic in the manner described in the above method embodiments.

Claims

1. A real-time privacy protection method for Internet of Things traffic, characterized in that: Applied to an edge node, the method comprises: Receive an encrypted request message and an identity identifier sent by an IoT device; wherein the encrypted request message is obtained by the IoT device by encrypting the request message using a homomorphic encryption algorithm based on the public key of the IoT device, and the request message is used to request a service of a specific IoT application; For the encryption request messages received within the maximum session time, determine the similarity index of the encryption request messages, and determine the encryption request messages whose similarity index difference does not exceed a preset threshold as similar encryption request messages; For multiple similar encryption request messages received within the maximum session time, the multiple similar encryption request messages are aggregated to obtain an aggregated encryption request message, and the identity identifier of each IoT device participating in the aggregation of the encryption request message is recorded; wherein the aggregated encryption request message is one of the multiple similar encryption request messages; The aggregate encryption request message and the identity identifier corresponding to the aggregate encryption request message are sent to the cloud-based centralized server, and the cloud-based centralized server decrypts the aggregate encryption request message according to the identity identifier corresponding to the aggregate encryption request message using the private key of the IoT device to which the identity identifier belongs to obtain a request message, determines the corresponding response data according to the obtained request message, and encrypts the response data using the public key of the edge node to obtain first ciphertext response data; When the first ciphertext response data sent by the cloud-based centralized server is received, the first ciphertext response data is decrypted according to the private key of the edge node to obtain the decrypted response data, and according to the recorded identity identifiers of each IoT device participating in the encryption request message aggregation, the response data is encrypted using the public key of each IoT device participating in the encryption request message aggregation to obtain second ciphertext response data with the same number of IoT devices participating in the encryption request message aggregation, and the obtained second ciphertext response data is sent to the corresponding IoT devices respectively, and the IoT device that receives the second ciphertext response data decrypts the second ciphertext response data using the private key of the IoT device to obtain the decrypted response data.

2. The method according to claim 1, characterized in that The identity of the IoT device is a pseudo identity; The pseudo identity of the IoT device is generated by the cloud-based centralized server according to the real identity of the IoT device and a random salt number during the registration process of the IoT device with the cloud-based centralized server.

3. The method according to claim 1, characterized in that The identity identifier of the IoT device is a pseudo identity identifier assigned to the IoT device by the cloud-based centralized server during the registration process of the IoT device with the cloud-based centralized server; For the encrypted request message and identity sent by any IoT device, the method further includes: According to the pseudo-identity identifier sent by the IoT device, the maintained pseudo-identity identifier list of the IoT device is queried to determine whether there is a matching target pseudo-identity identifier; wherein the pseudo-identity identifier list of the IoT device includes the pseudo-identity identifiers of the IoT device registered with the cloud-based centralized server; the pseudo-identity identifier of the IoT device is sent by the cloud-based centralized server to the edge node to which the IoT device is connected, and the pseudo-identity identifier list of the IoT device is maintained by the edge node according to the pseudo-identity identifier of the IoT device sent by the cloud-based centralized server; In the case where there is a matching target pseudo-identity, it is determined that the identity authentication of the IoT device is passed; wherein the encrypted request message sent by the IoT device that has passed the identity authentication participates in the calculation and subsequent processing of the similarity index; In the absence of a matching target pseudo-identity, it is determined that the identity authentication of the IoT device has failed, and a response to the encrypted request message sent by the IoT device that has failed the identity authentication is refused.

4. The method according to claim 1, characterized in that The determining of the similarity index of the encrypted request message includes: According to the encryption request message, a similarity index of the encryption request message is determined using a bilinear pairing algorithm of an elliptic curve.

5. The method according to claim 1, characterized in that Before encrypting the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation, the method further includes: Receive the public key sent by each IoT device, associate the identity of each IoT device, and cache the public key of each IoT device; The step of encrypting the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation includes: For any IoT device participating in encryption request message aggregation, query the cached public key of the IoT device based on the identity of the IoT device; Encrypt the response data using the public key of the IoT device; After encrypting the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation, the method further includes: Delete the cached public keys of each IoT device that participates in the encryption request message aggregation; or, The step of encrypting the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation includes: Obtaining the public key of each IoT device participating in the encryption request message aggregation from the cloud centralized server based on the recorded identity identifier of each IoT device participating in the encryption request message aggregation; The response data is encrypted using the public key of each IoT device participating in the encryption request message aggregation; or, Before encrypting the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation, the method further includes: Receive the identity and public key of the IoT device sent by the cloud-based centralized server, associate the identity of the IoT device, and save the public key of the IoT device; The step of encrypting the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity of each IoT device participating in the encryption request message aggregation includes: For any IoT device that participates in the encryption request message aggregation, query the stored public key of the IoT device based on the identity of the IoT device; The response data is encrypted using the public key of the IoT device.

6. A real-time privacy protection device for Internet of Things traffic, characterized in that: Deployed at an edge node, the device includes: A communication unit, configured to receive an encrypted request message and an identity identifier sent by an IoT device; wherein the encrypted request message is obtained by the IoT device by encrypting the request message using a homomorphic encryption algorithm based on the public key of the IoT device, and the request message is used to request a service of a specific IoT application; A determination unit, configured to determine, for the encryption request messages received within the maximum session time, a similarity index of the encryption request messages, and determine the encryption request messages whose similarity indexes differ by no more than a preset threshold as similar encryption request messages; an aggregation unit, configured to aggregate multiple similar encryption request messages received within the maximum session time to obtain an aggregated encryption request message, and record the identity of each IoT device participating in the aggregation of the encryption request message; wherein the aggregated encryption request message is one of the multiple similar encryption request messages; The communication unit is further used to send the aggregate encryption request message and the identity identifier corresponding to the aggregate encryption request message to the cloud-based centralized server, and the cloud-based centralized server decrypts the aggregate encryption request message according to the identity identifier corresponding to the aggregate encryption request message using the private key of the Internet of Things device to which the identity identifier belongs to obtain a request message, and determines the corresponding response data according to the obtained request message, and encrypts the response data using the public key of the edge node to obtain first ciphertext response data; The encryption and decryption unit is used to, when receiving the first ciphertext response data sent by the cloud centralized server, decrypt the first ciphertext response data according to the private key of the edge node to obtain the decrypted response data, and encrypt the response data according to the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity identifier of each IoT device participating in the encryption request message aggregation, to obtain the second ciphertext response data with the same number of copies as the number of IoT devices participating in the encryption request message aggregation; The communication unit is also used to send the obtained second ciphertext response data to the corresponding Internet of Things devices respectively, and the Internet of Things devices that receive the second ciphertext response data use the private key of the Internet of Things device to decrypt the second ciphertext response data to obtain decrypted response data.

7. The device according to claim 6, characterized in that The identity of the IoT device is a pseudo identity; The pseudo identity of the IoT device is generated by the cloud-based centralized server according to the real identity of the IoT device and a random salt number during the registration of the IoT device with the cloud-based centralized server; and / or, The identity identifier of the IoT device is a pseudo identity identifier assigned to the IoT device by the cloud-based centralized server during the registration process of the IoT device with the cloud-based centralized server; The device also includes: An identity authentication unit is used to query the maintained pseudo-identity list of IoT devices based on the pseudo-identity sent by any IoT device for an encrypted request message and an identity, and determine whether there is a matching target pseudo-identity; wherein the pseudo-identity list of IoT devices includes the pseudo-identity of IoT devices registered with the cloud-based centralized server; the pseudo-identity of the IoT device is sent by the cloud-based centralized server to the edge node to which the IoT device is connected, and the pseudo-identity list of the IoT device is maintained by the edge node based on the pseudo-identity of the IoT device sent by the cloud-based centralized server; if there is a matching target pseudo-identity, determine that the identity authentication of the IoT device is passed; wherein the encrypted request message sent by the IoT device that has passed the identity authentication participates in the calculation and subsequent processing of the similarity index; if there is no matching target pseudo-identity, determine that the identity authentication of the IoT device is not passed, and refuse to respond to the encrypted request message sent by the IoT device that has failed the identity authentication; and / or, The determining unit determines the similarity index of the encrypted request message, including: Determine a similarity index of the encrypted request message using a bilinear pairing algorithm of an elliptic curve according to the encrypted request message; and / or, The communication unit is also used to receive the public key sent by each IoT device; The encryption and decryption unit is also used to associate the identity of each IoT device and cache the public key of each IoT device; The encryption and decryption unit encrypts the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity identifier of each IoT device participating in the encryption request message aggregation, including: For any IoT device participating in encryption request message aggregation, query the cached public key of the IoT device based on the identity of the IoT device; Encrypt the response data using the public key of the IoT device; The encryption and decryption unit encrypts the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity identifier of each IoT device participating in the encryption request message aggregation, and further includes: Delete the cached public keys of each IoT device that participates in the encryption request message aggregation; or, The encryption and decryption unit encrypts the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity identifier of each IoT device participating in the encryption request message aggregation, including: Obtaining the public key of each IoT device participating in the encryption request message aggregation from the cloud centralized server based on the recorded identity identifier of each IoT device participating in the encryption request message aggregation; The response data is encrypted using the public key of each IoT device participating in the encryption request message aggregation; or, The communication unit is further used to receive the identity and public key of the IoT device sent by the cloud-based centralized server; The encryption and decryption unit is also used to associate the identity of the IoT device and store the public key of the IoT device; The encryption and decryption unit encrypts the response data using the public key of each IoT device participating in the encryption request message aggregation according to the recorded identity identifier of each IoT device participating in the encryption request message aggregation, including: For any IoT device that participates in the encryption request message aggregation, query the stored public key of the IoT device based on the identity of the IoT device; The response data is encrypted using the public key of the IoT device.

8. An electronic device, characterized in that: comprising a processor and a memory, wherein: Memory, used to store computer programs; A processor, for implementing the method according to any one of claims 1 to 5 when executing a program stored in a memory.

9. A computer program product, characterized in that The computer program product stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

10. A real-time privacy protection system for Internet of Things traffic, characterized in that: include: IoT devices, edge nodes, and cloud-based centralized servers; among them: The IoT device is used to encrypt the request message using a homomorphic encryption algorithm based on the public key of the IoT device to obtain an encrypted request message, and send the encrypted request message and the identity of the device to the edge node; wherein the request message is used to request a service of a specific IoT application; The edge node is used to receive the encryption request message and identity identifier sent by the IoT device; for the encryption request message received within the maximum session time, determine the similarity index of the encryption request message, and determine the encryption request message whose similarity index difference does not exceed a preset threshold as a similar encryption request message; The edge node is further configured to aggregate multiple similar encryption request messages received within the maximum session time to obtain an aggregated encryption request message, and record the identity of each IoT device participating in the aggregation of the encryption request message; wherein the aggregated encryption request message is one of the multiple similar encryption request messages; The edge node is further used to send the aggregate encryption request message and the identity identifier corresponding to the aggregate encryption request message to the cloud centralized server; The cloud-based centralized server is used to decrypt the aggregated encrypted request message according to the identity identifier corresponding to the aggregated encrypted request message using the private key of the IoT device to which the identity identifier belongs to obtain a request message, determine the corresponding response data according to the obtained request message, encrypt the response data using the public key of the edge node to obtain first ciphertext response data, and send the first ciphertext response data to the edge node; The edge node is further used to, upon receiving the first ciphertext response data sent by the cloud centralized server, decrypt the first ciphertext response data according to the private key of the edge node to obtain the decrypted response data, and encrypt the response data according to the recorded identity identifiers of the IoT devices participating in the encryption request message aggregation, respectively using the public keys of the IoT devices participating in the encryption request message aggregation, to obtain second ciphertext response data with the same number of copies as the number of IoT devices participating in the encryption request message aggregation, and send the obtained second ciphertext response data to the corresponding IoT devices respectively; The edge node is further configured to, upon receiving the second ciphertext response data, decrypt the second ciphertext response data using the private key of the IoT device to obtain decrypted response data.