WO2023151479A1

WO2023151479A1 - Data processing method, and device

Info

Publication number: WO2023151479A1
Application number: PCT/CN2023/073927
Authority: WO
Inventors: 郭保瑞
Original assignee: 阿里云计算有限公司; 阿里巴巴（中国）有限公司
Priority date: 2022-02-08
Filing date: 2023-01-31
Publication date: 2023-08-17
Also published as: CN114143117A; CN114143117B

Abstract

Provided in the embodiments of the present application are a data processing method and a device. The method comprises: a first Internet-of-Things device determining a shared key which is generated by negotiating with a second Internet-of-Things device in a first trusted execution environment; receiving second ciphertext and a second verification message, which are sent by the second Internet-of-Things device; verifying the second verification message in the first trusted execution environment on the basis of the shared key, and after the second verification message is successfully verified, decrypting the second ciphertext to obtain second exchange data; after it is determined, in the trusted execution environment, that at least one piece of second exchange data corresponding to the second Internet-of-Things device is obtained, executing a first processing operation on the basis of the at least one piece of second exchange data, so as to obtain a first processing result; and exporting the first processing result to an external execution environment. By using the technical solution provided in the embodiments of the present application, the data security is improved, and the aim of securely processing data is realized.

Description

Data processing method and equipment

This application claims the priority of the Chinese patent application with the application number 202210119023.9 and the application name "data processing method and equipment" submitted to the China Patent Office on February 08, 2022, the entire contents of which are incorporated in this application by reference.

technical field

The embodiments of the present application relate to the technical field of data processing, and in particular, to a data processing method and device.

Background technique

With the development of IoT technology, IoT devices have been widely used in various fields.

In practical applications, multiple IoT devices often have the need to exchange data for calculation, but direct transmission of plaintext data is often unsafe, easily leading to data leakage, and posing security risks.

Contents of the invention

Embodiments of the present application provide a data processing method and device, which are used to solve the problem of potential security risks in data in the prior art.

In the first aspect, an embodiment of the present application provides a data processing method, including:

The first IoT device determines a shared key generated through negotiation with the second IoT device in the first trusted execution environment;

receiving a second ciphertext and a second verification message sent by the second IoT device;

Verifying the second verification message based on the shared key in the first trusted execution environment, and decrypting the second ciphertext to obtain second exchange data after the second verification message is successfully verified. ;

After determining to obtain at least one second exchanged data corresponding to the second IoT device in the first trusted execution environment, performing a first processing operation based on the at least one second exchanged data to obtain a first processing result, and Exporting the first processing result to an external execution environment.

In the second aspect, an embodiment of the present application provides a data processing method, including:

The second IoT device determines the shared key generated through negotiation with the first IoT device;

generating a second ciphertext of the second exchange data and a second verification message of the second ciphertext based on the shared key;

sending the second ciphertext and the second verification message to the first IoT device; the first IoT device is configured to verify the shared key based on the shared key in the first trusted execution environment The second verification message of the second ciphertext is verified, and after the verification is successful, the second exchange data is obtained by decrypting the second ciphertext.

In a third aspect, an embodiment of the present application provides an Internet of Things device, including a storage component and a processing component; the storage component stores one or more computer instructions;

The processing component creates a trusted execution environment through its configured security unit or creates a sandbox and uses the sandbox as a trusted execution environment;

The one or more computer instructions are called and executed by the processing component to implement the data processing method as described in the first aspect above, or to implement the data processing method as described in the second aspect above.

In a fourth aspect, an embodiment of the present application provides an Internet of Things device, including a storage component, a processing component, and a secure element; the storage component stores one or more computer instructions;

The secure element is used to create a trusted execution environment called by the processing component;

In the embodiment of the present application, the first IoT device negotiates with the second IoT device in its first trusted execution environment to generate a shared key, and receives the second ciphertext and the second verification message sent by the second IoT device; and verifying the second verification message based on the shared key in the first trusted execution environment, and decrypting the second ciphertext to obtain a second exchange after the verification of the second verification message is successful. data; after determining to obtain at least one second exchange data corresponding to the second Internet of Things device in the first trusted execution environment, performing a first processing operation based on the at least one second exchange data to obtain first processing result, and export the first processing result to an external execution environment. In the embodiment of the present application, the data is transmitted encrypted and processed in a trusted execution environment to generate processing results, and only the processing results are exported to the external execution environment, thereby achieving the purpose of secure computing and effectively ensuring data security.

These or other aspects of the present application will be more concise and understandable in the description of the following embodiments.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present application. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

Figure 1a shows a schematic structural diagram of an embodiment of a data processing system provided by the present application;

Figure 1b shows a schematic structural diagram of another embodiment of a data processing system provided by the present application;

FIG. 2 shows a flowchart of an embodiment of a data processing method provided by the present application;

FIG. 3 shows a flowchart of another embodiment of a data processing method provided by the present application;

FIG. 4 shows a schematic structural diagram of an embodiment of a data processing device provided by the present application;

Fig. 5 shows a schematic structural diagram of another embodiment of a data processing device provided by the present application;

FIG. 6 shows a schematic structural diagram of an embodiment of an Internet of Things device provided by the present application;

Fig. 7 shows a schematic structural diagram of another embodiment of an Internet of Things device provided by the present application;

Fig. 8 shows a schematic structural diagram of another embodiment of an Internet of Things device provided by the present application.

Detailed ways

In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

In some processes described in the specification and claims of the present application and the description in the above-mentioned drawings, multiple operations appearing in a specific order are included, but it should be clearly understood that these operations may not be performed in the order in which they appear herein Execution or parallel execution, the serial numbers of the operations, such as 101, 102, etc., are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. Additionally, these processes can include more or fewer operations, and these operations can be performed sequentially or in parallel. It should be noted that the descriptions of "first" and "second" in this article are used to distinguish different messages, devices, modules, etc. are different types.

Taking the Internet of Things (IOT, Internet of Things) scenario as an example, practical applications often involve the use of data from multiple IoT devices to participate in calculations. Therefore, there is an IoT device that provides its own data to other IoT devices However, the data of different IoT devices is usually private data, and the plain text form will lead to data leakage and low data security. In particular, different IoT devices participating in the calculation belong to different data parties. For example, the data party can be an enterprise party, and resource data can be shared and transferred between different data parties with the help of IoT technology. However, the data party’s own resource data is usually It belongs to private data and does not want the other party to know, so how to realize the processing of data while protecting data privacy has become a technical problem that needs to be solved.

In order to realize data processing under the premise of ensuring data security, the inventor proposed the technical solution of this application after a series of studies. Data processing is performed in the execution environment to generate processing results, and only the processing results are exported to the external execution environment, thereby achieving the purpose of safe computing, realizing data processing and effectively ensuring data security.

Of course, the embodiment of the present application is not only applicable to the Internet of Things scenario, any two devices involving data transmission and calculation can be implemented according to the technical solution of the embodiment of the present application to ensure data security.

The following will clearly and completely describe the technical solutions in the embodiments of the application with reference to the drawings in the embodiments of the application. Apparently, the described embodiments are only some of the embodiments of the application, not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without making creative efforts belong to the scope of protection of this application.

FIG. 1 a shows a schematic diagram of a system architecture of a data processing system to which the technical solution of the embodiment of the present application can be applied; the system may include a first device 101 and a second device 102 . The first device 101 and the second device 102 may be any two devices that require data transmission and processing. In the IoT scenario, the first device 101 and the second device 102 may both be IoT devices, and in other application scenarios, the first device 101 and the second device 102 may also be, for example, client devices and server devices respectively.

Wherein, a communication connection may be directly established between the first device 101 and the second device 102, so as to realize data transmission.

In addition, as yet another embodiment, as shown in FIG. 1b, when the first device 101 and the second device 102 belong to different data parties, the first device 101 and the second device 102 may be located in different networks and cannot directly Communication, at this time, the first proxy system 103 of the first device 101 corresponding to the first data party and the second proxy system 104 of the second device 102 corresponding to the second data party can perform data forwarding, so as to realize the first device 101 and the second Communication between devices 102 .

In the technical solution of the embodiment of the present application, a Trusted Execution Environment (TEE, Trusted Execution Environment) can be created in the first device 101, which is named the first Trusted Execution Environment for convenience of description; it can also be created in the second device 102. There is a trusted execution environment, which is named the second trusted execution environment for convenience of description.

The first device and the second device may combine device types and/or security requirements to create a corresponding type of trusted execution environment. For example, the trusted execution environment can be a sandbox created in the device system; or the trusted execution environment can be created based on the built-in security unit of the CPU (central processing unit, central processing unit), such as based on Intel (a processor ) SGS (Software Guard Extension, software protection extension), ARM (a processor) Trustzone (trust zone) or AMD (a processor) PSP (Platform Security Processor, platform security processor), etc.; Or it may be created by an external secure element (SE, Secure Element) configured in the device, etc.

Among them, the trusted execution environment can be an operating environment that coexists with the operating system, which can run independently in the device, can ensure the security of data and codes in the trusted execution environment, and achieve the purpose of isolation from the external execution environment. In this paper The referenced external execution environment may refer to the operating system of the device.

In the Internet of Things scenario, the first device 101 or the second device 102 may be, for example, a sensor-type detection device, or a gateway device providing a gateway function, and any other Internet of Things device that requires multi-party data for calculation.

In the technical solution of the embodiment of the present application, the first device 101 can negotiate with the second device 102 in its first trusted execution environment to generate a shared key; the second device 102 can generate the second exchange data based on the shared key. ciphertext to and the second verification message of the second ciphertext, and send the second ciphertext and the second verification message to the first device 101; the second device 102 can perform the second verification based on the shared key in the first trusted execution environment The message is verified, and after the second verification message is verified successfully, it is decrypted from the second ciphertext to obtain the second exchange data; the first device 101 determines to obtain at least one second exchange data corresponding to the second device 102 in the first trusted execution environment After data, a first processing operation may be performed based on at least the at least one second exchanged data to obtain a first processing result, and the first processing result may be exported to an external execution environment. Encrypted data transmission is performed between the first device 101 and the second device 102, and the first device 101 performs decryption and data processing in a trusted execution environment, and only the first processing result is brought out of the external execution environment, which cannot be known by the external execution environment The second is to exchange data, so that data security can be guaranteed and data processing can be realized.

In the following one or more embodiments, the implementation details of the technical solutions of the embodiments of the present application are described in detail mainly by taking an Internet of Things scenario and taking the first device and the second device as Internet of Things devices as examples.

Fig. 2 is a flowchart of an embodiment of a data processing method provided by the embodiment of the present application. The technical solution of this embodiment is executed by the first Internet of Things device, and the method may include the following steps:

201: Determine the shared key generated through negotiation with the second Internet of Things device in the first trusted execution environment.

The first IoT device may combine the device type and/or security requirements to create a corresponding type of first trusted execution environment. For example, the first trusted execution environment may be a sandbox; or it may be created based on a CPU built-in security unit or based on a configured external security unit.

In order to further ensure security, especially when the first IoT device and the second IoT device need to exchange data with each other, and the first IoT device will also send data to the second IoT device, the second IoT device A second trusted execution environment can also be created, and the second IoT device can negotiate with the first IoT device in the second trusted execution environment to generate the shared key; the type of the second trusted execution environment can be sand box, or based on the built-in security unit of the CPU or based on the configuration of an external security unit, etc.

Wherein, the shared key may be generated through pre-negotiation between the first IoT device and the second IoT device, and of course, may also be generated in real time during each data transmission. Therefore, optionally, the method may also include: A trusted execution environment negotiates with the second IoT device to generate a shared key.

As an option, the shared key can be obtained through negotiation as follows:

First, the first IoT device generates the first private key and the first public key in the first trusted execution environment; wherein, the first private key can be stored in the first trusted execution environment; similarly, the second IoT device A second private key and a second public key may also be generated, optionally, the second IoT device may generate the second private key and the second public key in its second trusted execution environment;

Afterwards, the first IoT device exports the first public key to the external execution environment, and authenticates the first public key in the external execution environment to obtain the first public key certificate, and sends the first public key certificate to the second IoT device device; wherein, in the external execution environment, the digital signature technology can request the certificate authority (CA, Certificate Authority) to sign the first public key to obtain the first public key certificate of the first public key; similarly, the second Internet of Things device You can also enter the second public key Perform authentication to obtain the second public key certificate. Optionally, when the second public key is generated in the second optional execution environment, it can first be exported to the external execution environment of the second Internet of Things device. Key for authentication to obtain the first public key certificate;

Afterwards, the first IoT device obtains the second public key certificate sent by the second IoT device; the first IoT device also sends the first public key certificate to the second IoT device;

Afterwards, the first IoT device extracts the second public key from the second public key certificate; the first IoT device can verify the validity of the second public key certificate, and extract the second public key from it after the verification is valid; Similarly, the second Internet of Things device can also verify the validity of the first public key certificate, and extract the first public key from it after the verification is valid. The process of extracting the public key can be performed in a trusted environment;

Afterwards, the first IoT device generates a shared key by using a key agreement algorithm based on the first private key and the second public key in the first trusted execution environment. The second IoT device can also use the key agreement algorithm to generate the same shared key based on the second private key and the first public key. Optionally, the second IoT device can also be in the second trusted execution environment , based on the second private key and the first public key, a key agreement algorithm is used to generate the same shared key;

Wherein, the key agreement algorithm can for example adopt ECDH (Elliptic-Curve Diffie-Hellman, elliptic curve Diffie-Hellman) algorithm, certainly also can adopt other algorithm such as RSA (a kind of public key encryption algorithm), DHKA (Differ-Hellman). Hellman Key Exchange, Diffie-Hellman key exchange) algorithm, etc., this application does not specifically limit this.

Of course, the shared key can also be realized by other negotiation methods, such as being generated by the first IoT device, encrypted and sent to the second IoT device, and decrypted by the second IoT device, or generated by the second IoT device and sent to the second IoT device. The encrypted data is sent to the first IoT device and decrypted by the first IoT device, etc., or both the first IoT device and the second IoT device are generated according to the agreed algorithm, etc. This application does not impose specific restrictions on this.

202: Receive a second ciphertext and a second verification message sent by a second Internet of Things device.

The shared key is obtained through negotiation between the first IoT device and the second IoT device, and the second IoT device will also generate the shared key. Based on the shared key, the second exchange data to be sent can be encrypted etc. to obtain the second ciphertext and the second verification message of the second ciphertext.

The second exchange data to be sent may refer to at least part of the second data in the second IoT device to be transmitted to the first IoT device for participating in calculations. In practical applications, the second data has a large amount of data In some cases, the second data may also be divided into multiple second exchange data, the second exchange data to be sent may refer to any unsent second exchange data, etc., the second IoT device for each second exchange data For exchanging data, a corresponding second ciphertext and a second verification message can be generated based on the shared key, so as to be sent to the first IoT device in the form of the second ciphertext and the second verification message. Wherein, the encryption processing of the second exchange data may be realized by using any symmetric encryption algorithm, which is not specifically limited in this application. The second verification message can be used to realize the integrity protection of the second ciphertext, etc., and it can be an information digest of the second ciphertext, and the information digest can be, for example, MAC (Message Authentication Codes, information authentication code) algorithm to the second ciphertext generated MAC label and the like.

203: Verify the second verification message based on the shared key in the first trusted execution environment, and decrypt the second ciphertext to obtain second exchange data after the second verification message is successfully verified.

The first IoT device can first verify the second verification message, and if the verification is successful, it can decrypt the second exchange data from the second ciphertext. If the verification is successful, it can indicate that the second ciphertext is complete and has not been tampered with, so as to ensure data security. If the verification fails, it can be considered that there is a potential safety hazard, and the second ciphertext can be rejected. In addition, if the verification fails, the first resend request can be sent to the second Internet of Things device to request the second Internet of Things device to resend The erroneous second exchange data and so on.

In order to further improve security, after the first IoT device and the second IoT device generate a shared key, they can derive the first session key and the second session key based on the shared key, such as KDF (key Derivation function, key derivation function) for derivation. Of course, it can also be obtained by deriving the specified method agreed upon with the second IoT device, such as performing different specified transformations on the shared key to obtain the first session key and the second session key, etc., which are not discussed in this application Specific limits. The first IoT device may derive the first session key and the second session key from the shared key in its first trusted execution environment. The second Internet of Things device may use the first session key to encrypt the second exchange data to generate a second ciphertext, and use the second session key to generate a second verification message for the second exchange data, etc., so that step 203 may be: In a trusted execution environment, the second verification message is verified based on the second session key, and after the second verification message is successfully verified, the second exchange data is obtained by decrypting the second ciphertext based on the first session key. For example, the verification message of the second ciphertext may be generated by using the second session key. If the generated verification message is the same as the second verification message, it indicates that the second ciphertext is complete and has not been tampered with. If it succeeds, the integrity protection of the second exchange data is realized, and then the second exchange data can be decrypted from the second ciphertext based on the first session key.

204: After it is determined in the first trusted execution environment that at least one second exchanged data corresponding to the second Internet of Things device is obtained, execute a first processing operation based on the at least one second exchanged data, and obtain a first processing result.

It can be seen from the above description that the second data involved in the calculation in the second IoT device may be divided into at least one second exchange data and sent to the first IoT device respectively, and the first IoT device can follow the operation of step 203 Obtaining each second exchange data, the first IoT device can determine whether the reception is completed according to the quantity of the obtained second exchange data. Of course, when the second Internet of Things device sends the last second exchange data, it can Carrying the end identifier, the first IoT device may determine whether to obtain all the second exchange data according to whether the decrypted second exchange data carries the end identifier.

Afterwards, the first Internet of Things device may perform a corresponding processing operation based on the at least one second exchanged data, which is named as a first processing operation for convenience of description, so as to obtain a first processing result. Certainly, the at least one second exchanged data may also first be combined to obtain the second data of the second Internet of Things device, and then perform the first processing operation.

Optionally, in scenarios involving multi-party computing, the first IoT device may acquire multiple different IoT devices According to the data requirements in the Internet of Things, each Internet of Things device can be used as a second Internet of Things device to implement data transmission with the first Internet of Things device using the technical solution of the embodiment of the application. The first Internet of Things device can be based on at least one The at least one second exchange data sent by the IoT device is used to execute the first processing operation, thereby obtaining the first processing result. The present application does not specifically limit the data involved in the first processing operation, and the first IoT device may execute it based at least on at least one second exchange data sent by the second IoT device.

205: Export the first processing result to an external execution environment.

In this embodiment, after the first processing result is obtained in the first trusted execution environment, the first processing result is exported to the external execution environment, and the first IoT device can use the first processing result to perform subsequent operations, etc. . Since the data is encrypted and transmitted, and the data decryption operation is performed in a trusted execution environment, the external execution environment cannot be obtained, and only the first processing result is exported to the external execution environment, which not only realizes the data processing operation to obtain the processing result, but also ensures that the data Privacy and Security.

In a practical application, assuming that at least one second exchange data is user data in the second IoT device, user data is also maintained in the first IoT device, and the respective user data are private data, the first processing operation is specifically It can be to count the shared user data of the user data of the second IoT device and the user data of the first IoT device, the first processing result can be the shared user data, and only the shared user data is exported to the external execution environment, which can ensure Data security, and realize the requirement of shared user data determination.

The first IoT device may perform further processing on the first processing result in the external execution environment, or may resend the first processing result from the external execution environment to other processing systems for processing, etc., for example, the first processing result is shared In the case of user data, combined with the corresponding features of the second IoT device, personalized recommendations can be made for the shared user data. Of course, the above is just an example to illustrate the data processing scenarios that the technical solution of the present application can be applied to, and the present application is not limited to this.

In order to further improve security, the second IoT device may maintain a second count value, which matches the number of times data is sent. The second ciphertext can be obtained by encrypting the second exchange data and the current second count value of the second IoT device; in the case of obtaining the first session key and the second session key by deriving the shared key, it can first Combining the second exchange data and the current second count value to generate concatenated data, and then encrypting the concatenated data by using the first session key to obtain the second ciphertext. The combination format of the second exchange data and the second count value may be, for example, a TLV (tag, length, and value) format, etc., and of course it is not limited thereto.

Then the decryption from the second ciphertext to obtain the second exchange data after the second verification message is successfully verified may include: decrypting from the second ciphertext to obtain the second exchange data and the second count value after the second verification message is successfully verified; Check whether the second count value is correct; if the second count value is verified successfully, save the second exchange data, and send the first confirmation request to the second Internet of Things device; wherein, the first confirmation request can be used to notify The second IoT device sends the next second exchange data, or ends the sending process, and so on.

If the verification of the second count value fails, it can be considered that the second exchange data has an error and may be attacked by a third party. This can reject the second exchange data.

Optionally, after the verification of the second count value fails, the first IoT device may also send a first resend request to the second IoT device, so as to notify the second IoT device to resend the second exchanged data that has an error wait. Of course, the first IoT device may also delete the received second exchanged data to end the receiving process, or request the second IoT device to resend all the second exchanged data, etc.

Among them, the first IoT device checks whether the second count value is correct. There are many ways to implement it. For example, the second count value matches the number of times the second exchange data is sent by the second physical network device. If the verification of the second count value is successful, the number of verification times can be accumulated. The verification of the second count value can be to check whether the second count value matches the number of verification times, etc., wherein the number of times of verification can be less than the second count value, and can be compared with the second count value The value difference is 1; as another example, the second count value matches the number of times the second exchange data is sent by the second physical network device, and the first IoT device can save the second count value every time it successfully verifies the second count value , the verification of the second count value may be compared with the saved second count value, and if the difference is 1, it may be considered that the verification is successful. In addition, in order to further improve security, the first IoT device may also maintain the first count value. As yet another embodiment, checking whether the second count value is correct may include:

Check whether the second count value is the same as the current first count value; wherein, the initial values of the first count value and the second count value are the same, such as 0;

The method can also include:

If the verification of the second count value is successful, increment the first count value;

Then sending the first confirmation request to the second Internet of Things device includes:

generating a first encrypted value of the first count value and a third verification message of the first encrypted value based on the shared key;

Send a first confirmation request including the first encrypted value and the third verification message to the second Internet of Things device; the first confirmation request is also used to notify the second Internet of Things device that after the third verification message is successfully verified, based on the first encrypted value The first count value in updates the second count value.

Wherein, the first IoT device may set a first counter to generate a first count value, and the second physical network device may set a second counter to generate a second count value, and so on.

In the case of obtaining the first session key and the second session key by deriving the shared key, the first count value may be encrypted using the first session key to obtain the first encrypted value, and then the second session key may be used to generate A third verification message of the first encrypted value. Wherein, the first encrypted value and the third verification message may be combined in TLV format, for example, and then sent to the second IoT device.

In addition, the first IoT device may also have a need to transmit data to the second IoT device. Therefore, in some embodiments, the method may further include: in the first trusted execution environment, generating the first exchanging data The first ciphertext and the first verification message of the first ciphertext; the first ciphertext and the first verification message are sent to the second Internet of Things device; wherein, the first verification message is used by the second Internet of Things device in the second available In the letter execution environment, verification is performed based on the shared key, and the first exchange data is obtained by decrypting the first ciphertext after the verification is successful.

In order to ensure correct data transmission, the first IoT device may perform the above operation of sending the first exchanged data after determining to obtain at least one second exchanged data corresponding to the second IoT device, and may restore the first count value to initial value etc. Likewise, the second IoT device may restore the second count value to an initial value and the like after at least one second exchange data is completely sent.

Certainly, the second Internet of Things device may also send the second exchange data and the like after determining to obtain at least one piece of first exchange data corresponding to the first Internet of Things device. After the second Internet of Things device determines to obtain at least one first exchange data corresponding to the first Internet of Things device, the second count value can be restored to the initial value. Similarly, the first Internet of Things device completes sending at least one first exchange data Afterwards, the first count value may be restored to an initial value, etc. It can be seen from the above description that the first exchange data can be at least part of the first data that the first IoT device needs to send to the second IoT device to participate in the calculation, and the first data can be divided when the data volume is large A plurality of first exchanged data are obtained and sent respectively, so the method may further include:

segmenting the first data into at least one first exchange data;

Then in the first trusted execution environment, generating the first ciphertext of the first exchange data and the first verification message of the first ciphertext based on the shared key may be: for the first exchange data currently to be sent, based on the shared key A first ciphertext of the first exchange data and a first verification message of the first ciphertext are generated.

The first exchange data currently to be sent may refer to any first exchange data not sent by the first IoT device, or it may be based on the second resend request of the second IoT device, and the most recently sent first exchange data The data is again used as the first exchanged data to be sent currently. The second exchange data to be sent may refer to any unsent second exchange data, etc. For each first exchange data, the first IoT device may generate the corresponding first ciphertext and first ciphertext based on the shared key. The verification message is sent to the second IoT device in the form of the first ciphertext and the first verification message.

After the second trusted execution environment determines to obtain at least one first exchange data of the first Internet of Things device, the second IoT device may execute a second processing operation based on the at least one first exchange data to obtain a second processing result, and Export the second processing result to an external execution environment. The second IoT device decrypts and performs data processing in the trusted execution environment, and the external execution environment cannot obtain it. Only the second processing result is exported to the external execution environment, which not only realizes the data processing operation to obtain the processing result, but also guarantees the first - Data privacy and security of exchanged data.

Wherein, when the shared key is derived to obtain the first session key and the second session key, in the first trusted execution environment, the first ciphertext and the first ciphertext of the first exchange data are generated based on the shared key The first verification message of can be: in the first trusted execution environment, the first exchange data is encrypted into the first ciphertext by using the first session key, and the first verification message of the first ciphertext is generated by using the second session key .

In addition, in order to further ensure data security, the first IoT device may exchange the first The data and the current first count value are encrypted to generate the first ciphertext, and the first verification message of the first ciphertext is generated. After the second IoT device successfully verifies the first verification message, it decrypts the first ciphertext to obtain the first exchange Data and the first count value, first check whether the first count value is correct, after the verification is successful, the first exchange data can be saved, and a second confirmation request can be sent to the first IoT device, otherwise the first exchange can be rejected data, and may also send a second retransmission request to the first IoT device. The specific verification method, for example, can be to verify whether the first count value is the same as the current second count value, if they are the same, increment the second count value, and use the shared key to encrypt the second count value to generate a second encrypted value and Generate a fourth verification message of the second encrypted value. The second confirmation request may include the second encrypted value and the fourth verification message. After the first IoT device successfully verifies the fourth verification message, it may obtain the second encrypted value The second count value is obtained by decrypting in the middle, and the current first count value can be updated by using the second count value. Afterwards, the first IoT device may continue to send the next first exchange data or end the sending process. When sending the last first exchange data, the first IoT device may add an end identifier to the first exchange data before encrypting, so that the second Internet of Things device can determine whether the reception is complete based on the end identifier, and then execute the first processing operation etc.

The following describes the technical solution of this application from the perspective of the second Internet of Things device. Figure 3 is a flow chart of another embodiment of a data processing method provided by the embodiment of this application. The technical solution of this embodiment is provided by the second Internet of Things device To execute, the method may include the following steps:

301: Determine to negotiate with the first IoT device to generate a shared key.

Optionally, the second Internet of Things device may create a second trusted execution environment, and may negotiate with the first Internet of Things device to generate a shared key in the second trusted execution environment.

The first IoT device may generate the shared key through negotiation in the first trusted execution environment. The way of generating the shared key has been described in the foregoing embodiments, and will not be repeated here. The shared key may be generated through pre-negotiation, or may be generated in real time when the second data is sent, which is not limited in this application.

302: Generate a second ciphertext of the second exchange data and a second verification message of the second ciphertext based on the shared key.

Optionally, the second IoT device may derive the first session key and the second session key from the shared key. It may be that the first session key is used to encrypt the second exchange data to generate the second ciphertext, and the second session key is used to generate the second verification message of the second ciphertext.

303: Send the second ciphertext and the second verification message to the first IoT device.

Wherein, the first IoT device is used to verify the verification message of the second ciphertext based on the shared key in the first trusted execution environment, and decrypt the second ciphertext to obtain the second exchange data after the verification is successful, and Based on at least one second exchange data, execute a second processing operation to obtain a second processing result, and export the second processing result to an external execution environment.

In this embodiment, since the data is encrypted for transmission, and the data decryption operation is performed in the trusted execution environment of the first IoT device, the external execution environment cannot be obtained, and only the first processing result is exported to the external execution environment, which realizes data Processing operations to obtain processing results, and data privacy and security can be guaranteed.

In some embodiments, the method may also include:

segmenting the second data into at least one second exchange data;

Then, based on the shared key, the second ciphertext of the second exchange data and the verification message of the second ciphertext may be: for the second exchange data currently to be sent, use the shared key to encrypt the second exchange data to generate the second ciphertext. The ciphertext and the second verification message for generating the second ciphertext.

Optionally, in order to further improve security, for the second exchange data currently to be sent, using a shared key, encrypting the second exchange data to generate a second ciphertext and generating a second verification message of the second ciphertext may be :

For the second exchange data currently to be sent, encrypt the second exchange data and the current first count value to generate a second ciphertext and generate a second verification message of the second ciphertext; the first count value is used for the first Internet of Things The device is calibrated.

In some embodiments, the method may also include:

After receiving the first confirmation request sent by the first IoT device, the unsent second exchange data is used as the second exchange data to be sent; wherein, the first confirmation request is the verification of the first count value by the first IoT device send on success;

After receiving the first retransmission request sent by the first IoT device, the most recently sent second exchange data is re-used as the second exchange data to be sent; wherein, the first retransmission request is that the first IoT device counts Sent when the value verification fails or the verification of the second verification message fails.

Wherein, the verification of the second count value by the first Internet of Things device has been discussed in detail above, and will not be repeated here. In one of the verification methods, the first IoT device can maintain the first count value, the second IoT device can maintain the second count value, the first count value is the same as the initial value of the second count value, and the first IoT The networked device can specifically check whether the second count value is the same as the current first count value. After the verification is successful, the first count value can be incremented, and the incremented first count value can be encrypted based on the shared key to generate The first encrypted value and the third verification message. The first confirmation request sent by the first IoT device may include the first encrypted value and the third verification message. Therefore, in some embodiments, the method may further include: receiving The first confirmation request sent by the first Internet of Things device verifies the third verification message of the first encrypted value in the confirmation request based on the shared key, and decrypts the first encrypted value to obtain the first count value after the verification is successful ; Update the second count value with the first count value.

In addition, the first IoT device may also have a need to transmit data to the second IoT device, therefore, in some embodiments, the method may further include:

Receive the first ciphertext and the corresponding first verification message sent by the first IoT device;

Verifying the first verification message of the first ciphertext based on the shared key in the second trusted execution environment, and after the first verification message is successfully verified, decrypting from the first ciphertext to obtain the first exchange data;

After determining to obtain at least one first exchange data corresponding to the first IoT device in the second trusted execution environment, A second processing operation is performed based on the at least one first exchange data, and a result of the second processing is exported to an external execution environment.

Wherein, in order to ensure correct data transmission, the first IoT device may perform the operation of sending the first exchanged data after receiving at least one second exchanged data from the second IoT device; or the second IoT device may The operation of sending the second exchange data is performed after at least one piece of first exchange data from the first Internet of Things device is all received.

In order to further improve security, the first ciphertext may be obtained by encrypting the first exchange data and the current first count value. After the first verification message is successfully verified, decrypting the first ciphertext to obtain the first exchange data may be:

Check whether the first count value is correct; if the first count value is successfully verified, save the first exchange data, and send a second confirmation request to the first Internet of Things device; wherein, the second confirmation request can be used for Notifying the first IoT device to send the next second exchange data, or ending the sending process, etc.

If the verification of the second count value fails, it can be considered that the first exchange data has an error and may be attacked by a third party, so the second exchange data can be rejected.

Optionally, after the verification of the first count value fails, a second resend request may be sent to the first Internet of Things device, so as to notify the first Internet of Things device to resend the erroneous first exchange data and the like.

In order to further improve security, the checking whether the first count value is correct includes: checking whether the first count value is the same as the current second count value; wherein, the initial values of the first count value and the second count value are the same, for example, is 0; the method can also include:

If the verification of the first count value is successful, the second count value is incremented;

Then sending the second confirmation request to the second Internet of Things device includes:

generating a second encrypted value of the second count value and a fourth verification message of the second encrypted value based on the shared key;

Send a second confirmation request including a second encrypted value and a fourth verification message to the first IoT device; the second confirmation request is also used to notify the first IoT device that after the fourth verification message is successfully verified, based on the second encrypted value The second count value in updates the first count value.

The same or similar steps in the above embodiment shown in FIG. 3 and its related embodiments have been described in detail in the embodiment shown in FIG. 2 and its related embodiments, and will not be repeated here.

Taking the Internet of Things scenario as an example, combined with the system architecture diagram shown in Figure 1b, assuming that the first Internet of Things device is Device A, and the second Internet of Things device is Device B, an overall introduction to the technical solution of the embodiment of the present application is given.

Assume that device A and device B need to exchange data with each other.

Device A and device B can carry out key negotiation in their respective trusted execution environments, generate a shared key, and use the shared key for key derivation to obtain two session keys: the first session key and the second session key key.

Wherein, the shared key may be generated in advance, and of course, may also be generated in real time during data exchange, and the shared key generated for each data exchange may be the same or different.

The device B may divide the second data to be sent into multiple second exchange data, and the device B transmits and processes each second exchange data in the same way.

Device A may maintain a counter A in its memory, and device B may maintain a counter B in its memory. The initial values of counter A and counter B are the same, for example, may be 0.

For a second exchange data to be sent, device B, in its second trusted execution environment, encrypts the second exchange data and the second count value of the current counter B, generates a second ciphertext, and uses the second The second session key generates a second authentication message of a second ciphertext. After device B combines the second ciphertext and the second verification message, it may send it to device A via the first proxy system and the second proxy system.

After receiving the second ciphertext and the second verification message, device A imports it into its first trusted execution environment, uses the second session key to verify the second verification message in the first trusted execution environment, and the verification is successful. Use the first session key to decrypt the second ciphertext to obtain the second exchange data and the second count value. After that, check whether the second count value is the same as the current first count value of counter A. If they are the same, the value can be incremented. first count value, and use the first session key to generate the first encrypted value of the first count value and use the second session key to generate the third verification message of the first encrypted value, after that, the first proxy system and the second The second proxy system sends to device B a first confirmation request containing the first encrypted value and the third verification message. And if the second count value is different from the current first count value, the second exchange data may be rejected, and the first retransmission request may be sent to device A via the second proxy system and the second proxy system.

If device B receives the first confirmation request, it uses the second session key to verify the third verification message. After the verification is passed, it uses the first session key to decrypt the first encrypted value to obtain the first count value, and sends After the current second counting value is updated to the first counting value, the above process can be performed with the unsent second exchanged data as the second exchanged data to be sent. If the second exchanged data to be sent is the last second In the case of exchanging data, device B can also add an end identifier to the second exchange data, so that device A can determine whether the second data has been received or not based on the end identifier, and then when the receiving is completed, it can then check the received Execute the first processing operation on the at least one second exchange data to obtain the first processing result, and only export the first processing result to the external execution environment, so as to achieve the purpose of safely processing the second data.

If device B receives the first retransmission request, it may re-execute the above process and the like by using the most recently sent second exchange data as the second exchange data to be sent.

After the device A determines that the second data of the device B has been received, if there is a need to send data to the device B, the device A and the device B can reset their respective counters to an initial value of 0 at this time.

Device A divides the first data to be sent into multiple first exchanged data, and device A transmits and processes each first exchanged data in the same way.

For a first exchange data to be sent, device A sends the first exchange data in its first trusted execution environment After being combined with the first count value of the current counter A, encryption is performed to generate a first ciphertext, and a first verification message of the first ciphertext is generated by using the second session key. Device A may send to device B after combining the first ciphertext and the first verification message via the first proxy system and the second proxy system.

After receiving the first ciphertext and the first verification message, device B imports it into its second trusted execution environment, uses the second session key to verify the first verification message in the second trusted execution environment, and the verification is successful. Use the first session key to decrypt the first ciphertext to obtain the first exchange data and the first count value. After that, check whether the first count value is the same as the current second count value of counter B. If they are the same, the value can be incremented. second count value, and use the first session key to generate a second encrypted value of the second count value and use the second session key to generate a fourth verification message of the second encrypted value, after which, the first proxy system and the second The second proxy system sends to device A a second confirmation request including the second encrypted value and the fourth verification message. And if the first count value is different from the current second count value, the first exchange data may be rejected, and a second retransmission request may be sent to device A via the first proxy system and the second proxy system.

If device A receives the second confirmation request, it uses the second session key to verify the fourth verification message. After the verification is passed, it uses the first session key to decrypt the second encrypted value to obtain the second count value, and sends After the current first count value is updated to the second count value, the above-mentioned process can be performed with the unsent first exchange data as the first exchange data to be sent. If the first exchange data to be sent is the last first exchange data In the case of data, device A can also add an end identifier to the first exchanged data, so that device B can determine whether the first data has been received based on the end identifier, and then when the reception is completed, the received At least one first exchange data performs a second processing operation to obtain a second processing result, and only the second processing result is exported to an external execution environment, so as to achieve the purpose of safely processing the first data.

If device A receives the second retransmission request, it may use the most recently sent first exchange data as the second exchange data to be sent to perform the above process and so on.

In practical applications, for example, device A and device B belong to different enterprise devices, such as gateway devices in the Internet of Things. Enterprise A maintains the user information of its members in device A, such as communication numbers. B maintains the employee information of its members in device B, such as communication numbers; the employee information of enterprise A and enterprise B is private data, and the confidentiality requirements are high. Currently, there is a need to count the total members of enterprise A and enterprise B. At this time, enterprise A and enterprise B need to exchange the user information of all members, and seek the intersection of users to determine the purpose of common members. However, by adopting the technical solution of the embodiment of this application, the data is not only encrypted and transmitted, but also executed in a trusted manner. The calculation of user intersection is performed in the environment to determine the user information of the shared members, and only the user information of the shared members is exported to the external execution environment. Since the user information of the shared members is the existing data of enterprise A and enterprise B, it is guaranteed To ensure data security, enterprise A and enterprise B can further process the user information of shared members. For example, enterprise A can combine the characteristics of enterprise B to determine personalized recommendation information for shared members, and based on shared Member's user information, push personalized recommendation information, etc.

Through the technical solutions of the embodiments of the present application, data is encrypted for transmission, encryption, decryption, and data processing are performed in a trusted execution environment, thereby realizing data processing and ensuring data security.

Fig. 4 is a schematic structural diagram of an embodiment of a data processing device provided in an embodiment of the present application, the device may include:

The first determination module 401 is configured to determine the shared key generated through negotiation with the second IoT device in the first trusted execution environment;

The first receiving module 402 is configured to receive the second ciphertext and the second verification message sent by the second IoT device;

The first verification module 403 is configured to verify the second verification message based on the shared key in the first trusted execution environment, and decrypt the second exchange data from the second ciphertext after the second verification message is successfully verified;

The first processing module 404 is configured to perform a first processing operation based on the at least one second exchange data to obtain a first processing result after determining to obtain at least one second exchange data corresponding to the second Internet of Things device in the first trusted execution environment , and export the first processing result to an external execution environment.

In some embodiments, the second ciphertext is encrypted and obtained based on the second exchange data and the current second count value;

The first verification module decrypts the second ciphertext to obtain the second exchange data after the second verification message is successfully verified, including: after the second verification message is successfully verified, decrypts the second ciphertext to obtain the second exchange data and the second count value ;Check whether the second count value is correct; if the second count value is successfully verified, save the second exchange data, and send the first confirmation request to the second IoT device; if the second count value fails to verify, reject the second Exchange data.

In some embodiments, the first verification module checking whether the second count value is correct includes: checking whether the second count value is the same as the current first count value; wherein, the initial value of the first count value and the second count value same;

The device can also include:

The first update module is used to increment the first count value if the verification of the second count value succeeds;

Sending the first confirmation request to the second Internet of Things device by the first verification module includes: generating the first encrypted value of the first count value and the third verification message of the first encrypted value based on the shared key; sending to the second Internet of Things device including The first confirmation request for the first encrypted value and the third verification message; the first confirmation request is also used to notify the second Internet of Things device to update the first count value based on the first count value in the first encrypted value after the third verification message is successfully verified. Second count value.

In some embodiments, the device may also include:

The first derivation module is used to obtain the first session key and the second session key from the shared key in the first trusted execution environment;

The first verification module is specifically configured to verify the second verification message based on the second session key in the first trusted execution environment, and decrypt the second ciphertext based on the first session key after the second verification message is successfully verified. Obtain the second exchange data.

In some embodiments, the device may also include:

The first encryption module is configured to generate a first ciphertext of the first exchange data and a first verification message of the first ciphertext based on the shared key in the first trusted execution environment;

The first sending module is configured to send the first ciphertext and the first verification message to the second Internet of Things device; wherein, the first verification message is used by the second Internet of Things device based on the shared key in the second trusted execution environment Perform verification, and decrypt the first ciphertext to obtain the first exchange data after the verification is successful.

The data processing device shown in FIG. 4 can execute the data processing method described in the embodiment shown in FIG. 2 , and its implementation principles and technical effects will not be repeated here. The specific manner of performing operations by each module and unit of the data processing device in the above embodiment has been described in detail in the embodiment of the method, and will not be described in detail here.

Fig. 5 is a schematic structural diagram of another embodiment of a data processing device provided in an embodiment of the present application, the device may include:

The second determination module 501 is configured to determine the shared key generated through negotiation with the first IoT device;

The second encryption module 502 is configured to generate a second ciphertext of the second exchange data and a second verification message of the second ciphertext based on the shared key;

The second sending module 503 is configured to send the second ciphertext and the second verification message to the first IoT device; the first IoT device is used to verify the second ciphertext based on the shared key in the first trusted execution environment The second verification message is verified, and after the verification is successful, it is decrypted from the second ciphertext to obtain the second exchange data.

In some embodiments, the device may also include:

A segmentation processing module, configured to segment the second data into at least one second exchange data;

The second encryption module is specifically used to encrypt the second exchange data and the current second count value to generate a second ciphertext and generate a second verification message of the second ciphertext for the second exchange data currently to be sent, using a shared key ; The second count value is used for verification by the first IoT device.

In some embodiments, the second processing module is further configured to receive the first confirmation request sent by the first IoT device, and use the unsent second exchange data as the second exchange data to be sent; wherein, the first The confirmation request is sent by the first IoT device when the verification of the first count value is successful; the first retransmission request sent by the first IoT device is received, and the second exchange data sent most recently is re-used as the second exchange data to be sent ; Wherein, the first resending request is sent by the first IoT device when the verification of the first count value fails or the verification of the second verification message fails.

In some embodiments, the apparatus may further include: a second update module, configured to receive the first confirmation request sent by the first Internet of Things device, and perform the third verification message in the first confirmation request based on the shared key Verify, and after successful verification, decrypt the first encrypted value in the first confirmation request to obtain the first count value; the initial value of the first count value is the same as the initial value of the second count value; the first IoT device is used to After the count value is verified successfully, the first count value is incremented; and the second count value is updated by using the first count value.

In some embodiments, the second determination module is specifically configured to determine the The shared secret key generated by the device negotiation;

The device can also include:

The second receiving module is configured to receive the first ciphertext and the corresponding first verification message sent by the first IoT device;

The second verification module is configured to verify the first verification message based on the shared key in the second trusted execution environment, and after the verification succeeds, decrypt the first ciphertext to obtain the first exchange data;

The second processing module is configured to perform the first processing operation based on the at least one first exchange data after it is determined in the second trusted execution environment that at least one first exchange data corresponding to the first IoT device is obtained, and the first processing Results are exported to an external execution environment.

The data processing device shown in FIG. 5 can execute the data processing method described in the embodiment shown in FIG. 6 , and its implementation principles and technical effects will not be repeated here. The specific manner of performing operations by each module and unit of the data processing device in the above embodiment has been described in detail in the embodiment of the method, and will not be described in detail here.

In addition, the embodiment of the present application also provides an Internet of Things device, as shown in FIG. 6 , the device includes a storage component 601 and a processing component 602; the storage component 601 stores one or more computer instructions;

The processing component 602 creates a trusted execution environment through its configured security unit 603;

The one or more computer instructions are called and executed by the processing component to implement the data processing method of the embodiment shown in FIG. 2 above, or realize the data processing method of the embodiment shown in FIG. 3 above.

When the IoT device is used as the first IoT device in the above embodiment, the trusted execution environment created by it is the first trusted execution environment; when the IoT device is used as the second IoT device in the above embodiment , the trusted execution environment created by it is the second trusted execution environment.

Wherein, the processing component may be a central processing unit, such as Intel, ARM or AMD processing, and the trusted execution environment may be created based on Intel's SGS, ARM's Trustzone, or AMD's PSP.

In addition, the embodiment of the present application also provides an Internet of Things device, as shown in FIG. 7 , the device includes a storage component 701 and a processing component 702; the storage component 701 stores one or more computer instructions;

The processing component 702 creates a sandbox 703 and uses the sandbox 703 as a trusted execution environment;

In addition, the embodiment of the present application also provides an Internet of Things device, as shown in FIG. 8 , the device includes a storage component 801, a processing component 802, and a secure element 803; the storage component 801 stores one or more computer instructions;

The secure element 803 is used to create a trusted execution environment called by the processing component 802;

Of course, the above-mentioned Internet of Things device must also include other components, such as input/output interfaces, communication components, and the like. The input/output interface provides an interface between the processing component and the peripheral interface module, and the above peripheral interface module may be an output device, an input device, and the like. The communication component is configured to facilitate wired or wireless communication between the IoT device and other devices, and the like.

In addition, an embodiment of the present application also provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a computer, the data processing method in the above-mentioned embodiment shown in FIG. 2 or FIG. 3 can be implemented. The computer-readable medium may be contained in the electronic device described in the above embodiments; or it may exist independently without being assembled into the electronic device.

The embodiment of the present application also provides a computer program product, which includes a computer program carried on a computer-readable storage medium, and when the computer program is executed by a computer, it can realize the above-mentioned embodiments as shown in Figure 2 or Figure 3 data processing method. In such an embodiment, the computer program may be downloaded and installed from a network, and/or from removable media. When the computer program is executed by the processor, various functions defined in the system of the present application are performed.

The storage component in the above related embodiments may be configured to store various types of data to support operations at the terminal. The memory component can be implemented by any type of volatile or non-volatile memory device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.

The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without any creative effort.

Through the above description of the implementation manners, those skilled in the art can clearly understand that each implementation manner can use It can be realized by software plus necessary general-purpose hardware platform, of course, it can also be realized by hardware. Based on this understanding, the essence of the above technical solution or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products can be stored in computer-readable storage media, such as ROM/RAM, magnetic discs, optical discs, etc., including several instructions to make a computer device (which may be a personal computer, server, or network device, etc.) execute the methods described in various embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, rather than limiting them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent replacements are made to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present application.

Claims

A data processing method, characterized in that, comprising:

The first IoT device determines a shared key generated through negotiation with the second IoT device in the first trusted execution environment;

receiving a second ciphertext and a second verification message sent by the second IoT device;

Verifying the second verification message based on the shared key in the first trusted execution environment, and decrypting the second ciphertext to obtain second exchange data after the second verification message is successfully verified. ;

After determining to obtain at least one second exchanged data corresponding to the second IoT device in the first trusted execution environment, performing a first processing operation based on the at least one second exchanged data to obtain a first processing result, and Exporting the first processing result to an external execution environment.
The method according to claim 1, wherein the second ciphertext is encrypted and obtained based on the second exchange data and the current second count value;

The obtaining the second exchange data by decrypting the second ciphertext after the second verification message is successfully verified includes:

Decrypting from the second ciphertext to obtain second exchange data and a second count value after the second verification message is successfully verified;

verifying whether the second count value is correct;

If the verification of the second count value is successful, save the second exchange data, and send a first confirmation request to the second IoT device;

If the verification of the second count value fails, rejecting the second exchange data.
The method according to claim 2, wherein the checking whether the second count value is correct comprises:

Checking whether the second count value is the same as the current first count value; wherein, the initial values of the first count value and the second count value are the same;

The method also includes:

If the verification of the second count value is successful, increment the first count value;

The sending the first confirmation request to the second IoT device includes:

generating a first encrypted value of the first count value and a third verification message of the first encrypted value based on the shared key;

sending a first confirmation request including the first encrypted value and the third verification message to the second Internet of Things device; the first confirmation request is also used to notify the second Internet of Things device to After the third verification message is successfully verified, the second count value is updated based on the first count value in the first encrypted value.
The method according to claim 1, further comprising:

deriving a first session key and a second session key from the shared key in the first trusted execution environment;

Verifying the second verification message based on the shared key in the first trusted execution environment, and decrypting the second ciphertext to obtain the second verification message after the verification of the second verification message is successful. Exchange data includes:

In the first trusted execution environment, the second verification message is verified based on the second session key, and after the second verification message is successfully verified, based on the first session key, the Decrypt the second ciphertext to obtain the second exchange data.
The method according to claim 4, further comprising:

In the first trusted execution environment, generating a first ciphertext of the first exchange data and a first verification message of the first ciphertext based on the shared key;

Send the first ciphertext and the first verification message to the second IoT device; wherein, the first verification message is used by the second IoT device in the second trusted execution environment based on The shared key is verified, and after the verification is successful, the first exchange data is obtained by decrypting from the first ciphertext.
A data processing method, characterized in that, comprising:

The second IoT device determines the shared key generated through negotiation with the first IoT device;

generating a second ciphertext of the second exchange data and a second verification message of the second ciphertext based on the shared key;

sending the second ciphertext and the second verification message to the first IoT device; the first IoT device is configured to verify the shared key based on the shared key in the first trusted execution environment The second verification message of the second ciphertext is verified, and after the verification is successful, the second exchange data is obtained by decrypting the second ciphertext.
The method according to claim 6, further comprising:

segmenting the second data into at least one second exchange data;

The generation of the second ciphertext of the second exchange data based on the shared key and the second verification message of the second ciphertext include:

For the second exchange data currently to be sent, using the shared key, encrypt the second exchange data and the current second count value to generate a second ciphertext and generate a second verification message of the second ciphertext; The second count value is used for verification by the first IoT device.
The method according to claim 7, further comprising:

receiving the first confirmation request sent by the first IoT device, using the unsent second exchange data as the second exchange data to be sent; wherein, the first confirmation request is that the first IoT device Sending when the verification of the first count value is successful;

Receiving the first resend request sent by the first IoT device, reusing the second exchange data sent recently as the second exchange data to be sent; wherein, the first resend request is the The networking device sends it when the verification of the first count value fails or the verification of the second verification message fails.
The method according to claim 8, further comprising:

receiving the first confirmation request sent by the first Internet of Things device, verifying the third verification message in the first confirmation request based on the shared key, and after the verification is successful, from the first confirmation request Decrypt the first encrypted value in to obtain the first count value; the initial value of the first count value is the same as the initial value of the second count value; the first IoT device is used to check the second count value Incrementing the first count value after success;

The second count value is updated with the first count value.
The method according to claim 6, wherein the determination by the second Internet of Things device that the shared key generated through negotiation with the first Internet of Things device includes:

determining a shared key generated through negotiation with the first IoT device in the second trusted execution environment;

The method also includes:

receiving a first ciphertext and a corresponding first verification message sent by the first IoT device;

Verifying the first verification message based on the shared key in the second trusted execution environment, and after the verification succeeds, decrypting the first ciphertext to obtain the first exchange data;

After it is determined in the second trusted execution environment to obtain at least one first exchange data corresponding to the first IoT device, perform a first processing operation based on the at least one first exchange data, and store the first processing result Export to an external execution environment.
An Internet of Things device, characterized in that it includes a storage component and a processing component; the storage component stores one or more computer instructions;

The processing component creates a trusted execution environment through its configured security unit or creates a sandbox and uses the sandbox as a trusted execution environment;

The one or more computer instructions are called and executed by the processing component, so as to realize the data processing method according to any one of claims 1-5, or realize the data processing method according to any one of claims 6-10. Approach.
An Internet of Things device, characterized in that it includes a storage component, a processing component, and a security element; the storage component stores one or more computer instructions;

The secure element is used to create a trusted execution environment called by the processing component;

The one or more computer instructions are called and executed by the processing component, so as to realize the data processing method according to any one of claims 1-5, or realize the data processing method according to any one of claims 6-10. Approach.