WO2020173332A1

WO2020173332A1 - Trusted execution environment-based application activation method and apparatus

Info

Publication number: WO2020173332A1
Application number: PCT/CN2020/075688
Authority: WO
Inventors: 黄腾; 成亮; 李海东
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2019-02-27
Filing date: 2020-02-18
Publication date: 2020-09-03
Also published as: TW202109320A; CN111625829A

Abstract

Disclosed in the present invention is a trusted execution environment activation method, wherein the trusted execution environment is deployed in a terminal device. The method comprises: sending a terminal device identifier to a server; receiving activation information returned by a server, the activation information comprising an encrypted trusted identity identifier, a trusted key and an activation code, the trusted identity identifier and the trusted key corresponding to the terminal device identifier, and the activation code being generated according to the terminal device identifier; decrypting the activation information to obtain the trusted identity identifier, the trusted key and the activation code; and encrypting and storing the trusted identity identifier, the trusted key, and the activation code into a secure storage space. Also disclosed in the present invention are a trusted execution environment activation verification method, trusted execution environment-based application activation and activation verification methods, and corresponding apparatuses.

Description

Application activation method and device based on trusted execution environment

This application claims the priority of the Chinese patent application filed on February 27, 2019 with the application number 201910145498.3 and the invention title "Application activation method and device based on trusted execution environment", the entire content of which is incorporated into this application by reference . Technical field

The present invention relates to the technical field of application security, and in particular to an application activation method and device based on a trusted execution environment. Background technique

After the software is released, a way is needed to prevent the software from being cracked and misappropriated to ensure the software developers' own interests. Currently, the software is usually protected by a registration code, that is, the user first downloads and installs the trial version of the software, and then activates the software by applying for the registration code from the server. Later, when the user uses the software, the software will read the registration code file and judge whether the software is available according to the registration code file.

There are some problems with the above software activation scheme:

1. The registration code file is not encrypted and stored in the device, so that it can be copied to other devices in plain text, and the software installed on other devices can be illegally cracked. In addition, the content of the registration code file may be tampered with by users to illegally extend the number of uses or validity period of the software.

2. The registration code file is not bound to the device, so that the registration code file can be used in different devices, and the software installed on other devices is illegally cracked.

3. When the server transmits the registration code to the device, the content of the registration code file is not encrypted, which makes the registration code file easy to be monitored or forged.

Therefore, it is necessary to provide a more secure software activation method. Summary of the invention

To this end, the present invention provides an application activation method and device based on a trusted execution environment to try to solve or at least alleviate the above problems.

According to a first aspect of the present invention, there is provided a method for activating a trusted execution environment, the trusted execution environment being deployed in a terminal device, and the method includes: sending a terminal device identifier to a server; receiving a return from the server Activation information, the activation information includes an encrypted trusted identity, a trusted key, and an activation code, the trusted identity The share identifier and the trusted key correspond to the terminal device identifier, and the activation code is generated according to the terminal device identifier; the activation information is decrypted to obtain the trusted identity identifier, the trusted key, and the activation code ; Encrypting and storing the trusted identity, trusted key and activation code in a secure storage space.

According to a second aspect of the present invention, there is provided a method for activating a trusted execution environment, where the trusted execution environment is deployed in a terminal device, and the method includes: receiving a terminal device identifier sent by the terminal device; A trusted identity identifier and a trusted key corresponding to the terminal device identifier, and an activation code is generated according to the terminal device identifier; the trusted identity identifier, the trusted key, and the activation code are encrypted to generate activation information; The activation information is sent to the terminal device, so that the terminal device: decrypts the activation information to obtain a trusted identity, a trusted key, and an activation code, and transmits the trusted identity to the trusted The key and activation code are encrypted and stored in a secure storage space.

According to a third aspect of the present invention, there is provided an activation verification method of a trusted execution environment, which is executed in a trusted execution environment of a terminal device, and the method includes: obtaining a trusted identity, a trusted key, and a trusted The activation code of the execution environment, where the activation code includes use authority information and verification information of the trusted execution environment, and the verification information includes using the trusted key to pair the trusted identity, use authority information, and terminal The ciphertext generated by encrypting the device identification; obtaining the terminal device identification, and encrypting the trusted identity, usage authority information, and terminal device identification with a trusted key to generate a first ciphertext; if the first ciphertext is If the text is consistent with the verification information, and the current use environment of the terminal device matches the use authority information, the trusted execution environment is activated successfully.

According to a fourth aspect of the present invention, an application activation method based on a trusted execution environment is provided. The trusted execution environment is deployed in a terminal device, and the method includes: sending a trusted identity of the terminal device to a service End: receiving registration information returned by the server, where the registration information includes a registration code encrypted with a trusted key corresponding to the trusted identity, and the registration code is generated according to the trusted identity; Decrypt the registration information with the trust key to obtain a registration code; encrypt and store the registration code in a secure storage space.

According to a fifth aspect of the present invention, an application activation method based on a trusted execution environment is provided, the trusted execution environment is deployed in a terminal device, and the method includes: receiving a trusted identity sent by the terminal device; The trusted identity identifier generates a registration code; the trusted key corresponding to the trusted identity identifier is used to encrypt the registration code to generate registration information; and the registration information is sent to the terminal device so that The terminal device: decrypts the registration information with a trusted key to obtain a registration code; and encrypts and stores the registration code in a secure storage space.

According to a sixth aspect of the present invention, an application activation verification method based on a trusted execution environment is provided, which is executed in the trusted execution environment of a terminal device, and the method includes: obtaining a trusted identity, a trusted key, and To be verified The registration code of the application, where the registration code includes usage authority information and verification information, and the verification information is a ciphertext generated by using the trusted key to encrypt the trusted identity and usage authority information Use the trusted key to encrypt the trusted identity and use authority information to generate a first ciphertext; if the first ciphertext is consistent with the verification information, send the registration code To the application to be verified, so that the application determines whether the activation is successful according to whether the current use environment matches the use permission information.

According to a seventh aspect of the present invention, there is provided a terminal device, wherein a trusted execution environment is deployed on the terminal device, the trusted execution environment includes an activation management application, and the activation management application is adapted to execute the above A trusted execution environment activation method, a trusted execution environment activation verification method, a trusted execution environment-based application activation method, and a trusted execution environment-based application activation verification method.

According to an eighth aspect of the present invention, there is provided a server, including: at least one processor; and a memory storing program instructions, wherein the program instructions are configured to be executed by the at least one processor, so The program instructions include instructions for executing the trusted execution environment activation method and the application activation method based on the trusted execution environment as described above.

According to a ninth aspect of the present invention, an application activation system based on a trusted execution environment is provided, including: the terminal device as described above; and the server as described above.

The invention provides an application activation scheme based on a trusted execution environment. The trusted execution environment is an independent and trusted environment with an isolated hardware environment and an independent operating system, which can be used to store, process, and protect sensitive data. In the technical solution of the present invention, firstly, the trusted execution environment in the terminal device is activated. After the trusted execution environment has been activated, the trusted execution environment can provide trusted application activation to other applications of the terminal device. And activate the verification service to ensure the safety of other applications. The activation code of the trusted execution environment and the registration code of the application are encrypted and stored in the secure storage space through the trusted execution environment. The data in the secure storage space can only be read by the activation management application in the trusted execution environment, which ensures that Will not be illegally obtained and tampered with.

In the process of activating the trusted execution environment, the server generates the trusted identity and the trusted key of the terminal device. Subsequently, the trusted key is applied to the encrypted transmission process of the activation code of the trusted execution environment and the registration code of the application. The trusted key is transmitted only once between the terminal device and the server, that is, during and only during the process of activating the trusted execution environment, the server encrypts the generated trusted key and transmits it to the terminal device. In the process of activating the application by the trusted execution environment, the trusted key is no longer transmitted. Therefore, the trusted key is only stored in the terminal device and the server. Even if other devices monitor the registration information transmitted between the terminal device and the server, since the trusted key cannot be obtained, it cannot decrypt the registration information. The registration code is obtained, thereby further improving the transmission security of the application registration code. Both the activation code of the trusted execution environment and the registration code of the application are embedded with the trusted identity of the terminal device, thereby ensuring the uniqueness and non-copyability of the activation code and registration code of each terminal device. If the activation code and registration code are maliciously tampered with, the activation verification of the trusted execution environment of the terminal device and the application will fail. In addition, even if the activation code and registration code are copied to other terminal devices, they cannot be used to activate the trusted execution environment or applications of other terminal devices.

The above description is only an overview of the technical solution of the present invention. In order to understand the technical means of the present invention more clearly, it can be implemented in accordance with the content of the specification, and to make the above and other objectives, features and advantages of the present invention more obvious and understandable. In the following, specific embodiments of the present invention are specifically cited. Description of the drawings

In order to achieve the above and related purposes, this article describes certain illustrative aspects in conjunction with the following description and drawings. These aspects indicate various ways in which the principles disclosed herein may be practiced, and all aspects and their equivalents are intended to be Into the scope of the claimed subject matter. By reading the following detailed description in conjunction with the accompanying drawings, the above and other objectives, features and advantages of the present disclosure will become more apparent. Throughout this disclosure, the same reference numerals generally refer to the same parts or elements.

Fig. 1 shows a schematic diagram of a trusted execution environment activation system 100 according to an embodiment of the present invention; Fig. 2 shows a schematic diagram of an application activation system 200 based on a trusted execution environment according to an embodiment of the present invention;

FIG. 3 shows a flowchart of a method 300 (terminal device side) for activating a trusted execution environment according to an embodiment of the present invention;

FIG. 4 shows a schematic diagram of the activation process of a trusted execution environment according to an embodiment of the present invention; FIG. 5 shows a flowchart of a trusted execution environment activation method 500 (server side) according to an embodiment of the present invention ；

Fig. 6 shows a flowchart of a method 600 for activation verification of a trusted execution environment according to an embodiment of the present invention; Fig. 7 shows a schematic diagram of an activation verification process of a trusted execution environment according to an embodiment of the present invention; Fig. 8 Shows a flowchart of an application activation method 800 (on the terminal device side) based on a trusted execution environment according to an embodiment of the present invention;

Fig. 9 shows a schematic diagram of an application activation process based on a trusted execution environment according to an embodiment of the present invention; Fig. 10 shows an application activation method 1000 based on a trusted execution environment according to an embodiment of the present invention (server side ) Flow chart;

FIG. 11 shows a method 1100 for verifying application activation based on a trusted execution environment according to an embodiment of the present invention Flow chart of; and

Fig. 12 shows a schematic diagram of an application activation verification process based on a trusted execution environment according to an embodiment of the present invention. detailed description

Hereinafter, exemplary embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

The invention provides an application activation scheme based on a trusted execution environment. In the technical solution of the present invention, firstly, the trusted execution environment in the terminal device is activated. After the trusted execution environment has been activated, the trusted execution environment can provide trusted application activation to other applications of the terminal device. And activate the verification service to ensure the safety of other applications.

Fig. 1 shows a schematic diagram of a trusted execution environment activation system 100 according to an embodiment of the present invention. As shown in FIG. 1, the system 100 includes a terminal device 110 and a server 120. It should be noted that although the system 100 shown in FIG. 1 only includes one terminal device 110 and one server 120, those skilled in the art will understand that in practice, the system 100 may include any number of terminal devices 110 and server 120. The present invention does not limit the number of terminal devices 110 and server 120 included in the system 100.

The terminal device 110 may be specifically implemented as any device, such as a mobile phone, a tablet computer, a smart wearable device, a smart home appliance, a car machine, a drone, etc., but is not limited thereto. As shown in FIG. 1, a trusted execution environment (TEE for short) and a rich execution environment (REE for short) are deployed in the terminal device 110. The trusted execution environment and the rich execution environment have mutually isolated hardware and independent operating systems to meet the operating requirements of applications with different security levels. The hardware isolation between the trusted execution environment and the rich execution environment can be realized by, for example, the security extension technology of ARM TrustZone or C-SKY, but is not limited to this.

The operating system of the rich execution environment may be a general operating system such as Android, iOS, RTOS real-time operating system, etc., on which ordinary applications that do not require high security, such as instant messaging, photographing, and weather query, can be run. The operating system of the trusted execution environment is usually a closed, relatively simple secure operating system. Trusted applications with high security requirements are run on the operating system, such as fingerprint recognition, identity authentication, electronic payment, and smart locks. Wait. Trusted applications in the trusted execution environment can be called by ordinary applications in the rich execution environment to implement corresponding functions. Trusted applications cannot directly communicate with external parties (such as servers, other terminal devices, users, etc.), and It is necessary to use the common application in the rich execution environment as a communication relay, that is, the trusted application in the trusted execution environment communicates with the outside via the common application in the rich execution environment.

The server 120 may be any device that is used to provide a trusted execution environment online activation service to the terminal device 110, such as a physical server, or a computing instance deployed in the physical server, but is not limited to this. The server 120 is used to provide the terminal device 110 with an online activation service of a trusted execution environment. After the trusted execution environment is activated, the terminal device 110 can use the trusted execution environment to process and protect sensitive data.

In the embodiment of the present invention, the trusted execution environment includes an activation management application 112, and the activation management application 112 communicates with the server 120 via an interface application 113 deployed in the rich execution environment, and is used to activate the trusted execution environment. Specifically, the activation management application 112 reads the terminal device identification, and sends the terminal device identification to the server 120 via the interface application 113. The server 120 generates an activation code according to the terminal device identifier, generates a trusted identity identifier and a trusted key of the terminal device, and stores the trusted identity identifier and trusted key in association with the terminal device identifier. The trusted identity identifier is a character string that can represent the uniqueness of the device. It is used to uniquely identify the terminal device 110, and has the security attributes of being non-tamperable, non-forgeable, and globally unique. The trusted key is a character string derived through a specific algorithm according to a trusted identity, and is used to encrypt key information related to the terminal device 110. The server 120 encrypts the trusted identity, the trusted key, and the activation code to generate activation information, and sends the activation information to the activation management application 112 via the interface application 113. The activation management application 112 decrypts the activation information to obtain the trusted identity, the trusted key, and the activation code, and then encrypts and stores the trusted identity, the trusted key, and the activation code in the secure storage space 111. The secure storage space 111 is a designated space for storing files, and the files are stored in this location after being encrypted with a trusted key. In the embodiment of the present invention, the secure storage space 111 can and can only be accessed by the activation management application 112. After the trusted identity, the trusted key, and the activation code are encrypted and stored in the secure storage space 111, the trusted execution environment of the terminal device 110 is activated.

Common applications in the rich execution environment can call trusted applications in the trusted execution environment. When the trusted application is called, the called trusted application will further call the activation management application 112 to trigger the activation verification of the trusted execution environment. The activation management application 112 reads the trusted identity, the trusted key, and the activation code from the secure storage space 111, and verifies whether the trusted execution environment is successfully activated according to the trusted identity, the trusted key, and the activation code. Then, The verification result is returned to the trusted application called by the ordinary application. If the verification activation is successful, the called trusted application executes the call of the normal application, and returns the call result to the normal application.

For example, as shown in FIG. 1, the first common application 114 in the rich execution environment is a shopping application, and the first trusted application 115 is an electronic payment application. When the user selects some commodities in the first common application 114 and requires payment for purchase, the first common application 114 calls the first trusted application 115 to implement the electronic payment function. First Trusted Application 115 After being called, the activation management application 112 is triggered to perform activation verification of the trusted execution environment. The activation management application 112 reads the trusted identity, trusted key, and activation code from the secure storage space 111, verifies whether the trusted execution environment is successfully activated according to the trusted identity, trusted key, and activation code, and The verification result is returned to the first trusted application. If the verification activation is successful, the first trusted application 115 executes the call of the first common application 114 to implement the electronic payment function, and returns the call result (whether the payment is successful) to the first common application 114.

After the trusted execution environment has been activated, the trusted execution environment can provide activation and activation verification services to other applications of the terminal device 110, thereby ensuring the security of other applications. Fig. 2 shows a schematic diagram of an application activation system 200 based on a trusted execution environment according to an embodiment of the present invention. As shown in FIG. 2, the system 200 includes a terminal device 110 and a server 120. A trusted execution environment and a rich execution environment are deployed in the terminal device 110, and a second common application 116 is deployed in the rich execution environment. After the trusted execution environment of the terminal device 110 has been activated, the second common application 116 may be activated based on the trusted execution environment.

The server 120 further includes an application server 122 and an authentication server 124. The application server 122 is a server that provides methods and data calls to the second ordinary application 116, and can generate usage permission information (such as effective time, expiration time, available times, etc.) for activating the second ordinary application 116. The authentication server 124 is used to verify the identity of the terminal device 110, generate verification information according to the use authority information, and encrypt the use authority information and the verification information, and so on.

Specifically, the second common application 116 triggers the activation management application 112 to verify whether the trusted execution environment is successfully activated, and in the case that the trusted execution environment is successfully activated, sends the trusted identity of the terminal device to the application server 122. The application server 122 sends the trusted identity to the authentication server 124. The authentication server 124 verifies the identity of the terminal device 110, and returns the verification result to the application server 122. In the case that the authentication server 124 passes the verification, the application server 122 generates the use permission information of the second common application 116, and sends the use permission information to the authentication server 124. The authentication server 124 generates verification information according to the use permission information and the trusted identity, combines the use permission information and the verification information into a registration code, obtains the trusted key corresponding to the trusted identity, and uses the trusted key The registration code is encrypted to generate registration information, and the encrypted registration information is sent to the activation management application 112 via the application server 122 and the second common application 116 in sequence. The activation management application 112 obtains the trusted key from the secure storage space 111, uses the trusted key to decrypt the registration information to obtain the registration code, and encrypts and stores the registration code in the secure storage space 111. After the registration code is encrypted and stored in the secure storage space 111, the activation of the second common application 116 is completed.

FIG. 3 shows a flowchart of a method 300 for activating a trusted execution environment according to an embodiment of the present invention. The method 300 is executed in a trusted execution environment of a terminal device (for example, the aforementioned terminal device 110), for example, by the trusted execution ring The activation management application 112 in the environment is executed. As shown in FIG. 3, the method 300 starts at step S310.

In step S310, the terminal device identifier is sent to the server.

The terminal device identifier is used to uniquely identify a terminal device. Since the terminal device identifier is unique, it can also be called a device fingerprint. The terminal device identification can be, for example, the MAC (Media Access Control) address, CPU serial number, hard disk serial number and other information of the terminal device, or the calculation result obtained by processing the MAC address and CPU serial number of the terminal device, etc. , But not limited to this. The present invention does not limit the specific content of the terminal equipment identification. According to an embodiment, the terminal device identification is obtained by calling a corresponding data interface, and the data interface is usually provided by the manufacturer of the terminal device.

Specifically, step S310 is executed by the activation management application in the trusted execution environment. The activation management application 112 cannot directly communicate with the server, but sends the terminal device identification to the server via the interface application 113 in the rich execution environment.

According to an embodiment, in addition to sending the terminal device identification to the server, an authentication code can also be generated according to the terminal device identification, and the authentication code is sent to the server together, so that the server can verify the authentication code. After the code verification is passed, an activation code is generated according to the terminal device identification.

According to an embodiment, the authentication code includes a preset key, a first cipher text, and a first mapping value, where the first cipher text is a cipher generated by using the preset key to encrypt the session key and the terminal device identifier. Here, the first mapping value is a value obtained by using a preset mapping function to map the session key and the terminal device identifier. According to an embodiment, the preset key is one of the configuration information of the activation management application 112, and accordingly, the value of the preset key can be read from the configuration information of the activation management application. The session key is generated by the terminal device, for example, by the activation management application 112. According to an embodiment, when the activation management application 112 communicates with the server, the activation management application 112 will generate a token for this communication, the token including the preset key read from the configuration information And the generated session key. According to the preset key and the session key in the token, the first ciphertext can be determined, and then the authentication code can be generated. Those skilled in the art can understand that in addition to the preset key and the session key, the token may also include other information, such as the application identifier of the activation management application 112, the version number of the activation management application 112, and the purpose of the preset key. , Preset key types, etc. The present invention does not limit the specific information included in the token.

In addition, it should be noted that the encryption algorithm used to generate the first ciphertext and the mapping function used to generate the first mapping value can be set by those skilled in the art, and the present invention does not limit this. For example, the encryption algorithm used to generate the first ciphertext may be an AES encryption algorithm, and the mapping function used to generate the first mapping value may be a hash algorithm, but is not limited to this.

After the authentication code is generated, the authentication code and the terminal device identification are sent to the server side so that the server side can authenticate The code is verified, the session key is recovered from it, and it is ensured that the authentication code and the terminal device identifier are not intercepted or maliciously tampered with during the transmission process. According to an embodiment, the server can verify the authentication code according to the following method: read a preset key from the authentication code, and use the preset key to decrypt the first cipher text in the authentication code to obtain Session key and terminal device identification. Subsequently, the preset mapping function is used to calculate the second mapping value of the session key and the terminal device identifier, and if the second mapping value is consistent with the first mapping value in the authentication code, the authentication code verification is passed.

Those skilled in the art can understand that in order to enable the server to verify the authentication code, certain algorithm parameters need to be disclosed between the terminal device and the server, such as the encryption algorithm used to generate the first ciphertext, and the first mapping value to be generated. The mapping function used, etc. These parameters can be agreed upon in advance by the terminal device and the server before the terminal device transmits the terminal device identification and authentication code to the server; these parameters can also be used as fields of the authentication code and transmitted to the server together with the authentication code; etc. The present invention does not limit the specific method for synchronizing algorithm parameters between the terminal equipment and the server.

Table 1 shows an example of the authentication code AuthCode1 in the activation process of the trusted execution environment:

Table 1

In Table 1, the preset key is Provisioning Key1, and the first cipher text is Pro vis Encryp t (Session Key + Dev_FP), that is, the first cipher text is the provisioning key Provisioning Key1 used to pair the session key Session Key The ciphertext obtained by encrypting with the terminal device identifier Dev_FP. The first mapping value is Hash_Sha256 (Session Key + Dev_FP), that is, the first mapping value is the hash value of the session key Session Key calculated by using the SHA256 algorithm and the terminal device identifier Dev_FP.

Those skilled in the art can understand that in practice, in addition to the fields listed in Table 1, the authentication code AuthCode1 may also include other fields, such as the application identifier of the activation management application 112, the version number of the activation management application 112, and the preset password. For key usage, preset key types, etc., the present invention does not limit the number and types of fields included in the authentication code.

After sending the authentication code AuthCode1 and the terminal device identification Dev_FP shown in Table 1 to the server, the server will verify the authentication code: first, read the provisioning key Provisioning Key1 from the authentication code AuthCode1. Subsequently, the Provisioning Key is used to decrypt the first ciphertext Provis io ning_Key_Encrypt (Session Key + Dev_FP) to recover the Session Key. Finally, the SHA256 algorithm is used to calculate the hash value of the recovered session key Session Key and the terminal device identification Dev_FP. If the hash value is the same as the first in AuthCode1 If the mapping values are consistent, the AuthCode1 verification is successful.

Subsequently, in step S320, the activation information returned by the server is received, the activation information includes the encrypted trusted identity, the trusted key, and the activation code, where the trusted identity, the trusted key, and the terminal device identity are the same Correspondingly, the activation code is generated according to the terminal device identification.

The trusted identity and the trusted key are generated by the server. The server generates a trusted identity and a trusted key, and stores the trusted identity and the trusted key in association with the terminal device identity. A trusted identity identifier is a string that can represent the uniqueness of a device. It is used to uniquely identify a terminal device, and it has the security attributes of being non-tamperable, non-forgeable, and globally unique. The trusted key is a character string derived through a specific algorithm based on the trusted identity, which is used to encrypt key information related to the terminal device corresponding to the trusted identity.

The activation code is generated according to the terminal device identification, and is used to activate the trusted execution environment of the terminal device. According to an embodiment, the activation code includes use permission information and verification information of the trusted execution environment.

The use authority information of the trusted execution environment is used to mark the use authority of the trusted execution environment. The usage authority information may include, for example, effective time, expiration time, and available times, but is not limited to this. When the usage authority information includes effective time and expiration time, the terminal device can use the trusted execution environment normally only within the time range from effective time to expiration time. Outside the time range from effective time to expiration time, the terminal device is trusted The execution environment is in an inactive state, and the trusted execution environment is not available. When the use authority information includes the available times, the terminal device can only call the trusted execution environment within the available times. If the terminal device calls the trusted execution environment for the available times, the trusted execution environment will be in an inactive state. The letter execution environment is not available. Those skilled in the art can understand that the usage authority information can be configured, and it can include at least one of effective time, expiry time, and available times, and can also include other information except effective time, expiry time, and available times. The invention does not limit the specific content included in the usage right information.

The verification information is used to verify the activation code to ensure that the activation code has not been illegally tampered with. According to an embodiment, the verification information includes a cipher text generated by encrypting the trusted identity identifier, the use authority information, and the terminal device identifier using a trusted key. The present invention does not limit the specific encryption algorithm used to generate the verification information. For example, the encryption algorithm used to generate the verification information may be, for example, the HMAC (Hash-based Message Authentication Code) algorithm, but is not limited thereto.

Table 2 shows an example of the activation code ActiCode: Table 2

In Table 2, the usage authority information includes effective time Stimel, expiration time Etimel, and available times Timesl. The verification information is HMAC (IDkey, Dev_FP + ID + Stimel + Etimel + Timesl), that is, the verification information is based on the HMAC algorithm, using the trusted key IDkey to identify the terminal device Dev_FP, the trusted identity ID, and the effective time Stimel, expiration time Etimel, and available times Timesl are encrypted message digests generated.

Those skilled in the art can understand that, in practice, in addition to the fields listed in Table 2, the activation code ActiCode may also include other fields, such as the algorithm used to encrypt the activation code ActiCode using a trusted key IDkey, The key check value KCV (Key Checksum Value) for verifying whether the trusted key IDkey has been tampered with, and the algorithm for generating the key check value KCV, etc., the present invention is concerned with the number and types of fields included in the activation code There are no restrictions.

In step S320, the activation information includes an encrypted trusted identity, a trusted key, and an activation code. According to an embodiment, the activation information may be generated according to the following steps: encrypt the activation code with a trusted key to generate the activation code ciphertext; use the session key to encrypt the trusted identity, the trusted key, and the activation code The text is encrypted to generate activation information. The session key is determined in advance by the terminal device and the server. For example, the session key can be agreed upon in advance by the terminal device and the server before the terminal device transmits the terminal device identification and authentication code to the server; for another example, see Table 1. Session Key Session Key can be implicit in the authentication code AuthCode1 and transferred to the server; etc. The invention does not limit the generation of the session key and the transfer method of the session key between the terminal device and the server. In addition, the encryption algorithm used to generate the activation code ciphertext and the activation information can be any encryption algorithm, and the present invention does not limit this.

Taking Table 1 and Table 2 as examples, the steps for generating activation information are as follows: First, use the trusted key IDkey to encrypt the activation code ActiCode to generate the activation code ciphertext ActiCode’. Subsequently, the session key Session Key determined from the authentication code AuthCode1 is used to encrypt the trusted identity ID, the trusted key IDkey, and the activation code ciphertext ActiCode' to generate activation information.

After the activation information is received in step S320, step S330 is executed.

In step S330, the activation information is decrypted to obtain a trusted identity, a trusted key, and an activation code. The process of decrypting the activation information is opposite to the process of encrypting the activation information on the server side. According to an implementation For example, the activation information is decrypted according to the following steps: First, the activation information is decrypted using the session key to obtain the trusted identity, the trusted key, and the activation code cipher; then, the trusted key is used to pair the activation code The ciphertext is decrypted to obtain the activation code.

Taking Table 2 as an example, the decryption process of the activation information is as follows: First, the session key Session Key is used to decrypt the activation information to obtain the trusted identity ID, the trusted key IDkey, and the activation code ciphertext ActiCode'. Subsequently, the trusted key IDkey is used to decrypt the activation code ciphertext ActiCode' to obtain the activation code ActiCode.

After the trusted identity, the trusted key and the activation code are obtained in step S330, step S340 is executed.

In step S340, the trusted identity, the trusted key, and the activation code are encrypted and stored in a secure storage space. The data in the secure storage space can only be read by the activation management application 112 in the trusted execution environment, which ensures that the data therein will not be illegally obtained or tampered with.

According to an embodiment, after obtaining the trusted identity, trusted key, and activation code in step S330, instead of directly encrypting and storing the trusted identity, trusted key, and activation code in a secure storage space, The activation code is first verified according to the terminal device identification to ensure that the activation information has not been illegally tampered with during the transmission process between the server and the terminal device. After the activation code is verified, the trusted identity, the trusted key and the activation code are encrypted and stored in the secure storage space.

According to an embodiment, the activation code can be verified according to the following steps: using a trusted key to encrypt the trusted identity identifier, usage authority information, and terminal device identifier to generate a second cipher text; if the second cipher text is associated with the activation code If the verification information in is consistent, the activation code verification is passed.

Taking Table 2 as an example, the verification process of the activation code ActiCode is as follows: Obtain the terminal device identification Dev_FP (for example, obtain it through the data interface provided by the terminal device manufacturer). Based on the HMAC algorithm, the terminal device identifier Dev_FP, the trusted identity identifier ID, the effective time Stimel, the expiration time Etimel, and the available times Times 1 are encrypted using the trusted key IDkey to generate the second ciphertext. If the second cipher text is consistent with the verification information in the activation code, the activation code verification is passed. Otherwise, the verification fails.

After the trusted identity, the trusted key, and the activation code are encrypted and stored in the secure storage space 111, the trusted execution environment of the terminal device is activated. The trusted identity, trusted key, and activation code in the secure storage space 111 can only be read by the activation management application 112 in the trusted execution environment.

Fig. 4 shows a schematic diagram of an activation process of a trusted execution environment according to an embodiment of the present invention. In FIG. 4, the secure storage space 111, the activation management application 112, and the interface application 113 are all located in the terminal device 110, the activation management application 112 is a trusted application in a trusted execution environment, and the interface application 113 is a normal application in a rich execution environment .

In step S401, the user triggers the activation management application 112 to perform the trusted execution environment through the interface application 113 Activation verification.

In steps S402 and S403, the activation management application 112 reads the activation code ActiCode of the trusted execution environment from the secure storage space 111, verifies the ActiCode, and sends the verification result to the interface application 113 in step S404. If ActiCode is not stored in the secure storage space 111 or the activation management application 112 fails to verify the ActiCode, then in step S404, the activation management application 112 will return to the interface application 113 a result that the trusted execution environment is not activated. Subsequently, step S405 is executed.

In step S405, the interface application 113 triggers the activation management application 112 to activate the trusted execution environment. In step S406, the activation management application 112 obtains the terminal device identifier Dev_FP through the interface provided by the terminal device manufacturer, obtains the preset key Provisioning Key1, and generates the session key Session Key.

In step S407, the activation management application 112 generates an authentication code according to the terminal device identifier Dev_FP

AuthCode1, as shown in Table 1, AuthCode1 includes a preset key Provisioning Key1, a first ciphertext Pro vis io ning_Ke y_Encrypt (S es io n Key + Dev_FP), and a first mapping value Has h_S ha256 (S es s io n Key + Dev_FP)

In step S408, the activation management application 112 sends the terminal device identification Dev_FP and the authentication code AuthCode1 to the interface application 113.

In step S409, the interface application 113 and the terminal device identification Dev_FP AuthCodel authentication code transmitted to the server 120 _o

In step S410, the server 120 verifies the authentication code AuthCode1: First, read the preset key Provisioning Key1 from the authentication code AuthCode1. Subsequently, the Provisioning Key1 is used to decrypt the first cipher text Provisioning_Key_Encrypt (Session Key + Dev_FP) to recover the session key Session Key. Finally, the SHA256 algorithm is used to calculate the hash value of the recovered session key Session Key and the terminal device identifier Dev_FP. If the hash value is consistent with the first mapping value in AuthCode1, the authentication of AuthCode1 is successful. Subsequently, step S411 is executed.

In step S411, the server 120 generates a trusted identity ID and a trusted key IDkey, and stores the trusted identity ID and the trusted key IDkey in association with the terminal device identity Dev_FP.

In step S412, the server 120 generates the activation code ActiCode according to the terminal device identifier Dev_FP. As shown in Table 2, the ActiCode includes the effective time Stimel, the expiration time Etimel, the available times Timesl, and the verification information HMAC (IDkey, Dev_FP + ID + Stimel). + Etimel +Timesl ). Use the trusted key IDkey to encrypt the activation code ActiCode to generate the activation code ciphertext ActiCode'; use the session key Session Key to encrypt the trusted identity ID, the trusted key IDkey, and the activation code ciphertext ActiCode', Generate activation information. In step S413, the server 120 sends the activation information to the interface application 113.

In step S414, the interface application 113 sends the activation information to the activation management application 112.

In step S415, the activation management application 112 uses the Session Key to decrypt the activation information to obtain the trusted identity ID, the trusted key IDkey, and the activation code ciphertext ActiCode'. Subsequently, the trusted key IDkey is used to decrypt the activation code ciphertext ActiCode' to obtain the activation code ActiCode.

In step S416, the activation management application 112 obtains the terminal device identifier Dev_FP through the data interface provided by the manufacturer of the terminal device. Based on the HMAC algorithm, a trusted key IDkey is used to encrypt the terminal device identifier Dev_FP, the trusted identity identifier ID, the effective time Stimel, the expiration time Etimel, and the available times Times 1, to generate the second ciphertext. If they are consistent with the activation of the second ciphertext verification information is verified by the activation code, step S417 _o

In steps S417 and S418, the activation management application 112 encrypts and stores the trusted identity ID, the trusted key IDkey, and the activation code ActiCode in the secure storage space 111, and the trusted execution environment is successfully activated.

In step S419, the activation management application 112 feeds back the result of successful activation of the trusted execution environment to the interface application

113.

Fig. 5 shows a flowchart of a method 500 for activating a trusted execution environment according to an embodiment of the present invention. method

500 is executed in the server (for example, the server 120 shown in FIG. 1), which corresponds to the aforementioned method 300 executed in the terminal device. As shown in FIG. 5, the method 500 starts at step S510.

In step S510, the terminal device identifier sent by the terminal device is received.

Since the activation management application 112 cannot directly communicate with the server, but needs to communicate with the server via the interface application 113 in the rich execution environment. Therefore, in step S510, the server receives the terminal device identifier from the interface application 113.

According to an embodiment, in step S510, in addition to receiving the terminal device identification, the authentication code sent by the terminal device is also received, and the authentication code is generated according to the terminal device identification. The authentication code is verified, and after the authentication code is verified, step S520 is executed to generate an activation code according to the terminal device identifier.

According to an embodiment, the authentication code includes a preset key, a first cipher text, and a first mapping value, where the first cipher text is a cipher generated by using the preset key to encrypt the session key and the terminal device identifier. Here, the first mapping value is a value obtained by using a preset mapping function to map the session key and the terminal device identifier. Correspondingly, the server can verify the authentication code according to the following method: read the preset key from the authentication code, and use the preset key to decrypt the first cipher text in the authentication code to obtain the session key And terminal device identification. Subsequently, the preset mapping function is used to calculate the second mapping value of the session key and the terminal device identification, if the second mapping value is compared with the first mapping in the authentication code If the values are consistent, the authentication code verification is passed.

For the specific implementation steps of the generation and verification of the authentication code, please refer to the relevant description of the aforementioned step S310, which will not be repeated here.

Subsequently, in step S520, a trusted identity identifier and a trusted key corresponding to the terminal device identifier are generated, and an activation code is generated according to the terminal device identifier.

The trusted identity identifier is used to uniquely identify a terminal device, and it has security attributes that cannot be tampered with, cannot be forged, and are globally unique. The trusted key is a key corresponding to a trusted identity, which is used to encrypt key information. The server can generate the trusted identity and the trusted key according to any algorithm, and the present invention does not limit the specific algorithm used to generate the trusted identity and the trusted key. After the trusted identity and the trusted key are generated, the trusted identity and the trusted key are associated and stored.

The use authority information of the trusted execution environment is used to mark the use authority of the trusted execution environment. The usage authority information may include, for example, effective time, expiration time, and available times, but is not limited to this.

The verification information is used to verify the activation code to ensure that the activation code has not been illegally tampered with. According to an embodiment, the verification information includes a cipher text generated by encrypting the trusted identity identifier, the use authority information, and the terminal device identifier using a trusted key. The present invention does not limit the specific encryption algorithm used to generate the verification information. For example, the encryption algorithm used to generate the verification information may be, for example, the HMAC algorithm, but is not limited thereto. For an example of the activation code ActiCode, please refer to Table 2 above, and will not be repeated here.

Subsequently, in step S530, the trusted identity, the trusted key and the activation code are encrypted to generate activation information.

According to one embodiment, the activation code is encrypted with a trusted key to generate the activation code ciphertext; the session key is used to encrypt the trusted identity, the trusted key, and the activation code ciphertext to generate activation information . For the specific steps of generating the activation information, reference may be made to the aforementioned related description of step S320, which will not be repeated here.

Subsequently, in step S540, the activation information is sent to the terminal device, so that the terminal device: decrypts the activation information to obtain the trusted identity, the trusted key, and the activation code, and the trusted identity, the trusted key And the activation code are encrypted and stored in a secure storage space.

For the specific implementation process of step S540, reference may be made to the relevant descriptions of the foregoing steps S330 and 340, which are not repeated here. Common applications in the rich execution environment can call trusted applications in the trusted execution environment. When a trusted application is called, the called trusted application will further call the activation management application 112 to trigger the activation of the trusted execution environment Verification.

FIG. 6 shows a flowchart of a method 600 for verifying activation of a trusted execution environment according to an embodiment of the present invention. The method 600 is executed in the trusted execution environment of the terminal device, for example, executed by the activation management application 112 in the trusted execution environment. As shown in FIG. 6, the method 600 starts at step S610.

In step S610, a trusted identity, a trusted key, and an activation code of a trusted execution environment are obtained. The activation code includes use authority information and verification information of the trusted execution environment, and the verification information includes using a trusted key pair The ciphertext generated by encrypting the trusted identity identifier, usage authority information, and terminal device identifier.

According to an embodiment, the activation management application 112 reads the trusted identity ID, the trusted key IDkey, and the activation code ActiCode of the trusted execution environment from the secure storage space 111. The activation code ActiCode further includes usage authority information. For example, as shown in Table 2, the activation code ActiCode includes the effective time Stimel, the expiration time Etimel, and the available times Times 1, and the verification information HMAC (IDkey, Dev_FP + ID + Stimel + Etimel + Timesl) _{o The} verification information is based on the HMAC algorithm, using a trusted key IDkey to encrypt the terminal device ID Dev_FP, trusted identity ID, effective time Stimel, expiration time Etimel and available times Time si The generated message digest.

Subsequently, in step S620, the terminal device identifier is obtained, and the trusted identity identifier, the use right information, and the terminal device identifier are encrypted by using the trusted key to generate a third ciphertext.

According to an embodiment, the terminal device identifier Dev_FP is obtained through the data interface provided by the terminal device manufacturer, and based on the HMAC algorithm, the trusted key IDkey is used to identify the trusted identity ID, effective time Stimel, expiration time Etimel, and available times Times 1 and the terminal device identifier Dev_FP are encrypted to generate the third ciphertext.

Subsequently, in step S630, if the third ciphertext is consistent with the verification information, and the current use environment of the terminal device matches the use authority information, the trusted execution environment is activated successfully.

For example, the use authority information includes effective time, expiration time, and available times. Accordingly, the current use environment of the terminal device includes information such as time and used times. If the current time of the terminal device is within the range of effective time to expiration time, and the number of times used is less than or equal to the number of available times, the current use environment of the terminal device matches the use authority information.

Fig. 7 shows a schematic diagram of an activation verification process of a trusted execution environment according to an embodiment of the present invention. In FIG. 7, the secure storage space 111, the activation management application 112, the first trusted application 115, and the first common application 114 are all located in the terminal device 110, and the activation management application 112 and the first trusted application 115 are in a trusted execution environment The first common application 114 is a common application in a rich execution environment.

In step S701, the first normal application 114 initiates a call request to the first trusted application 115. In step S702, the first trusted application 115 triggers the activation management application 112 to perform activation verification of the trusted execution environment.

In steps S703 and S704, the activation management application 112 reads the trusted identity ID, the trusted key IDkey, and the activation code ActiCode of the trusted execution environment from the secure storage space 111. As shown in Table 2, ActiCode comprising effective time Stimel, expiration time Etimel, the available number of check information Times 1 and HMAC (IDkey, Dev_FP + ID + Stimel + Etimel + Timesl) o

In step S705, the activation management application 112 obtains the terminal device identifier Dev_FP through the data interface provided by the manufacturer of the terminal device. Based on the HMAC algorithm, a trusted key IDkey is used to encrypt the trusted identity ID, the expiration time Stimel, the expiration time Etimel, the available times Timesl, and the terminal device identity Dev_FP to generate the third ciphertext. If the third cipher text is consistent with the verification information in the activation code, the activation code verification is passed, and the trusted execution environment has been activated.

In step S706, the activation management application 112 sends the result that the trusted execution environment has been activated to the first trusted application 115.

In step S707, the first trusted application 115 executes the call requested by the first normal application 114.

In step S708, the first trusted application 115 returns the call result to the first normal application 114.

After the trusted execution environment has been activated, the trusted execution environment can provide activation and activation verification services to other applications of the terminal device 110, thereby ensuring the security of other applications.

FIG. 8 shows a flowchart of a method 800 for application activation based on a trusted execution environment according to an embodiment of the present invention. The method 800 is executed in the trusted execution environment of the terminal device, for example, executed by the activation management application 112 in the trusted execution environment. The method 200 can be used to activate common applications in a rich execution environment, such as the second common application 116 shown in FIG. 2. As shown in FIG. 8, the method 800 starts at step S810.

In step S810, the trusted identity of the terminal device is sent to the server.

The trusted identity is stored in the secure storage space 111 of the terminal device, and it can only be read by a specific trusted application in the trusted execution environment, such as the activation management application 112. After the activation management application 112 obtains the trusted identity, it sends the trusted identity to the server 120 through the application to be activated in the rich execution environment (for example, the second common application 116 in FIG. 2).

According to an embodiment, before sending the trusted identity to the server, it is necessary to verify whether the trusted execution environment is successfully activated; in the case that the trusted execution environment is successfully activated, then the trusted identity of the terminal device is sent To the server.

Specifically, the steps shown in the foregoing method 600 can be followed to verify whether the trusted execution environment is successfully activated. If If the trusted execution environment is successfully activated, the trusted execution environment is available, and the application to be activated can be activated based on the trusted execution environment. If the activation of the trusted execution environment fails, the trusted execution environment is unavailable. At this time, the aforementioned method 300 needs to be executed to activate the trusted execution environment. After the trusted execution environment is activated, the method 800 of the present invention can be executed.

According to one embodiment, in addition to sending the trusted identity to the server, step S810 also generates an authentication code based on the trusted identity, and sends the authentication code and the trusted identity to the server, so that the server can pair The authentication code is verified, and after the authentication code is verified, the registration code is generated according to the trusted identity.

According to an embodiment, the authentication code includes a preset key, a fourth cipher text, and a third mapping value, where the fourth cipher text is a cipher text generated by using the preset key to encrypt the trusted identity, and the first The three-mapping value is a value obtained by using a preset mapping function to map the trusted identity. According to an embodiment, the preset key is one of the configuration information of the activation management application 112, and accordingly, the value of the preset key can be read from the configuration information of the activation management application. According to an embodiment, when the activation management application 112 communicates with the server, the activation management application 112 will generate a token for this communication, the token including the preset key read from the configuration information . According to the preset key in the token, the fourth ciphertext can be determined, and then the authentication code can be generated. Those skilled in the art can understand that in addition to the preset key and the session key, the token may also include other information, such as the application identifier of the activation management application 112, the version number of the activation management application 112, and the purpose of the preset key. , Preset key types, etc. The present invention does not limit the specific information included in the token.

In addition, it should be noted that the encryption algorithm used to generate the fourth ciphertext and the mapping function used to generate the third mapping value can be set by those skilled in the art, and the present invention does not limit this. For example, the encryption algorithm used to generate the fourth ciphertext may be an AES encryption algorithm, and the mapping function used to generate the third mapping value may be a hash algorithm, but is not limited to this.

After the authentication code is generated, the authentication code and the trusted identity are sent to the server side, so that the server can verify the authentication code to ensure that the authentication code and the trusted identity are not tampered with during transmission. According to an embodiment, the server can verify the authentication code according to the following method:

Read the preset key from the authentication code, use the preset key to decrypt the fourth cipher text to obtain the trusted identity, and use the preset mapping function to calculate the fourth mapping value of the trusted identity. The fourth mapping value is consistent with the third mapping value in the authentication code, and the authentication code verification is passed.

Table 3 shows an example of the authentication code AuthCode2 in the application activation process based on the trusted execution environment: table 3

In Table 3, the preset key is Provisioning Key2, the fourth ciphertext is Provisioning_Key_Encrypt(ID), SP, and the fourth ciphertext is the ciphertext obtained by using the provisioning key Provisioning Key2 to encrypt the trusted identity ID. . The third mapping value is Hash_Sha256(ID), that is, the third mapping value is the hash value of the trusted identity ID calculated using the SHA256 algorithm.

Those skilled in the art can understand that, in practice, in addition to the fields listed in Table 3, the authentication code AuthCode2 may also include other fields, such as the application identifier of the activation management application 112, the version number of the activation management application 112, and the preset secret. For key usage, preset key types, etc., the present invention does not limit the number and types of fields included in the authentication code.

After sending the authentication code AuthCode2 shown in Table 3 to the server, the server will verify the authentication code: First, read the provisioning key Provisioning Key2 from the authentication code AuthCode2. Subsequently, the fourth cipher text Provisioning_Key_Encrypt (ID) is decrypted using Provisioning Key2 to obtain a trusted identity ID. Finally, the SHA256 algorithm is used to calculate the hash value of the trusted identity ID. If the hash value is consistent with the third mapping value in AuthCode2, the AuthCode2 verification is successful.

Subsequently, in step S820, the registration information returned by the server is received, the registration information includes the registration code encrypted with the trusted key corresponding to the trusted identity, and the registration code is generated based on the trusted identity.

The registration code is generated according to the trusted identity and used to activate the application to be activated. According to an embodiment, the registration code includes usage permission information and verification information of the application to be activated.

The usage permission information of the application is used to mark the usage permission of the application. The usage authority information may include, for example, effective time, expiration time, and available times, but is not limited thereto. When the usage authority information includes effective time and expiration time, the user can use the application normally only within the time range of effective time to expiration time, and the application is not available outside the time range of effective time to expiration time. When the usage permission information includes the available times, the user can only use the application within the available times. If the user uses the application for the available times, the application is no longer available. Those skilled in the art can understand that the usage authority information can be configured, and it can include at least one of effective time, expiration time, and available times, and can also include other information except effective time, expiration time, and available times. The invention does not limit the specific content included in the usage permission information of the application.

The verification information is used to verify the registration code to ensure that the registration code has not been illegally tampered with. According to one embodiment, The verification information includes a cipher text generated by using a trusted key to encrypt the trusted identity and usage authority information. The present invention does not limit the specific encryption algorithm used to generate the verification information. For example, the encryption algorithm used to generate the verification information may be, for example, the HMAC (Hash-based Message Authentication Code) algorithm, but is not limited thereto.

Table 4 shows an example of the registration code License:

Table 4

In Table 4, the usage authority information of the application includes the effective time Stime2, the expiration time Etime2, and the available times Times2. The verification information is HMAC (IDkey, ID + Stime2 + Etime2 + Times2), that is, the verification information is based on the HMAC algorithm, using a trusted key IDkey to identify the trusted identity ID, effective time Stime2, expiration time Etime2, and available times The message digest generated by Times2 encryption.

In step S820, the registration information includes the registration code encrypted with the trusted key corresponding to the trusted identity. That is, the server first determines the trusted key corresponding to the trusted identity, and then uses the trusted key to encrypt the registration code to generate registration information.

It should be noted that the process of encrypting the registration code to generate registration information in method 800 is slightly different from the process of encrypting the activation code to generate activation information in method 300. In the method 300, the activation code is double-encrypted by the trusted key and the session key; in the method 800, the registration code is only single-encrypted by the trusted key. This is because in the method 300, the trusted key is generated for the first time, and the trusted key needs to be sent to the terminal device along with the activation code. In order to ensure that the trusted key is not intercepted or tampered with, after using the trusted key to encrypt the activation code, it is also necessary to use the session key to encrypt the trusted key to make the trusted key invisible to the outside. In method 800, the trusted key is not transmitted, but is only stored in the terminal device and the server. Even if other devices monitor the registration information transmitted between the terminal device and the server, since the trusted key cannot be obtained, It also cannot decrypt the registration information to obtain the registration code. Therefore, in the method 800, the security of the registration code can be ensured by only single-encrypting the registration code with the trusted key, and there is no need to use the session key for secondary encryption.

Subsequently, in step S830, the trusted key is used to decrypt the registration information to obtain the registration code.

Subsequently, in step S840, the registration code is encrypted and stored in a secure storage space. The data in the secure storage space can only be read by the activation management application 112 in the trusted execution environment, which ensures that the data in it will not be illegally obtained. And tampering.

According to one embodiment, after the registration code is obtained in step S830, the registration code is not directly encrypted and stored in a secure storage space, but the registration code is first verified according to the trusted identity identifier to ensure that the registration information is on the server and the terminal device. No illegal tampering during the transmission. After the registration code is verified, the registration code is encrypted and stored in the secure storage space.

According to an embodiment, the registration code can be verified according to the following steps: a trusted key is used to encrypt the trusted identity and usage authority information to generate a fifth cipher text; if the fifth cipher text is verified with the registration code If the information is consistent, the registration code verification is passed.

Taking Table 4 as an example, the verification process of the registration code license is as follows: Obtain the trusted key IDkey, based on the HMAC algorithm, use the trusted key IDkey to perform the trusted identity ID, effective time Stime2, expiration time Etime2, and available times Times2 Encrypt and generate the fifth ciphertext. If the fifth cipher text is consistent with the verification information in the registration code, the registration code verification is passed. Otherwise, the verification fails.

After the registration code of the application to be activated is encrypted and stored in the secure storage space 111, the activation of the application to be activated is completed. The registration code in the secure storage space 111 can only be read by the activation management application 112 in the trusted execution environment.

Fig. 9 shows a schematic diagram of an application activation process based on a trusted execution environment according to an embodiment of the present invention. In FIG. 9, the secure storage space 111, the activation management application 112, and the second common application 116 are located in the terminal device, the activation management application 112 is a trusted application in a trusted execution environment, and the second common application 116 is a trusted application in a rich execution environment. The application to be activated. The application server 122 and the authentication server 124 are located on the server. The application server 122 is used to provide methods and data calls to the second ordinary application 116, and generate use permission information of the second ordinary application 116 (for example, effective time, expiration time, available times, etc.). The authentication server 124 is used to verify the identity of the terminal device 110, and to encrypt related data.

In step S901, the second normal application 116 initiates a request to the activation management application 112 to initialize the trusted execution environment. The activation management application 112 performs activation verification on the trusted execution environment based on the request. If the trusted execution environment activation verification is successful, step S902 is executed.

In steps S902 and S903, the activation management application 112 reads the trusted identity identification ID and the trusted key IDkey from the secure storage space 111.

In step S904, the activation management application 112 generates the authentication code AuthCode2 according to the trusted identity ID. As shown in Table 3, AuthCode2 includes the preset key Provisioning Key2, the fourth cipher text ProvisioninLKey_Encrypt(ID), and the third mapping value. Hash_Sha256(ID).

In step S905, the activation management application 112 sends the trusted identity ID and the authentication code AuthCode2 to The second general application 116.

In step S906, the second common application 116 sends the trusted identity ID and the authentication code AuthCode2 to the application server 122.

In step S907, the application server 122 to the trusted identity ID and the authentication code to the authentication server transmits AuthCode2 124 _o

In step S908, the authentication server 124 verifies the authentication code AuthCode2: First, read the preset key Provisioning Key2 from the authentication code AuthCode2. Subsequently, the fourth cipher text Provisioning_Key_Encrypt (ID) is decrypted using Provisioning Key2 to obtain a trusted identity ID. Finally, the SHA256 algorithm is used to calculate the hash value of the trusted identity ID. If the hash value is consistent with the third mapping value in AuthCode2, the AuthCode2 verification is successful.

In step S909, the authentication server 124 returns the successful verification result of the authentication code AuthCode2 to the application server 122.

In step S910, the application server 122 generates the use permission information of the second common application 116, referring to Table 4. The use permission information includes the effective time Stime2, the expiration time Etime2, and the available times Times2.

In step S911, the application server 122 sends the generated usage authority information to the authentication server 124. In step S912, the authentication server 124 generates verification information, referring to Table 4, the verification information is HMAC (IDkey, ID + Stime2 + Etime2 + Times2). Subsequently, the use permission information and verification information are combined to form the registration code License. Look up the trusted key IDkey corresponding to the trusted identity ID, and use the IDkey to encrypt the License to generate registration information.

In steps S913-S915, the authentication server 124 sequentially passes through the application server 122 and the second common application 116, and sends the registration information to the activation management application 112.

In step S916, the activation management application 112 uses the trusted key IDkey to decrypt the registration information to obtain the registration code License. Use the trusted key IDkey to encrypt the trusted identity ID, the effective time Stime2, the expiration time Etime2, and the available times Times2 to generate the fifth ciphertext. If the fifth ciphertext is consistent with the verification information in the License, the registration code verification is passed, and step S917 is executed.

In steps S917 and S918, the activation management application 112 encrypts and stores the registration code License in the secure storage space 111, and the second common application 116 is successfully activated.

In step S919, the activation management application 112 feeds back the result of the successful activation of the second common application 116 to the second common application 116.

FIG. 10 shows a flow of an application activation method 1000 based on a trusted execution environment according to an embodiment of the present invention Cheng Tu. The method 100 is executed in the server (for example, the server 120 shown in FIG. 2), and corresponds to the method 800 executed in the terminal device, and is suitable for the application to be activated (for example, the second ordinary application 116 shown in FIG. 2). ) To activate.

According to an embodiment, the server further includes an application server (for example, the application server 122 shown in FIG. 2) and an authentication server (for example, the authentication server 124 shown in FIG. 2), and the application server and the authentication server have a division of labor Collaborate to achieve application activation based on a trusted execution environment. The application server can directly communicate with the application to be activated, and is used to provide methods and data calls to the application to be activated, and generate usage permission information of the application to be activated (for example, effective time, expiration time, available times, etc.). The authentication server usually does not directly communicate with the application to be activated, and is used to verify the identity of the terminal device 110, and to encrypt related data.

As shown, the method begins at step 101000 S lOlO _o

In step S1010, the trusted identity sent by the terminal device is received.

The trusted identity is stored in the secure storage space 111 of the terminal device, and it can only be read by a specific trusted application in the trusted execution environment, such as the activation management application 112. After the activation management application 112 obtains the trusted identity, it is sent to the application server through the application to be activated. Correspondingly, the application server receives the trusted identity sent by the application to be activated.

According to an embodiment, in step S1010, in addition to receiving the trusted identity, the authentication code sent by the terminal device is also accepted, and the authentication code is generated according to the trusted identity. The authentication code is verified, and after the authentication code is verified, step S520 is executed to generate a registration code according to the trusted identity.

According to an embodiment, after the application server 122 receives the trusted identity and the authentication code sent by the second common application 116, it forwards the trusted identity and the authentication code to the authentication server 124, and the authentication server 124 To verify the authentication code. For the specific verification process of the authentication code, reference may be made to the relevant description of the foregoing step S810, which is not repeated here.

Subsequently, in step S1020, a registration code is generated according to the trusted identity.

According to an embodiment, the registration code includes use permission information and verification information of the application to be activated, where the use permission information is used to mark the use permission of the application, which may include, for example, effective time, expiration time, available times, etc. But it is not limited to this. The verification information is used to verify the registration code to ensure that the registration code has not been illegally tampered with. According to an embodiment, the verification information includes a cipher text generated by using a trusted key to encrypt the trusted identity identifier and the use authority information.

According to an embodiment, the usage permission information in the registration code is generated by the application server 122. After the application server 122 generates the usage permission information, it sends the usage permission information to the authentication server 124, which is generated by the authentication server 124 Into the verification information. For the specific generation process of the usage authority information and the verification information, reference may be made to the relevant description of the foregoing step S820, which is not repeated here.

Subsequently, in step S1030, the trusted key corresponding to the trusted identity is used to encrypt the registration code to generate registration information.

According to an embodiment, step S1030 is performed by the authentication server 124.

Subsequently, in step S1040, the registration information is sent to the terminal device, so that the terminal device: decrypts the registration information with the trusted key to obtain the registration code; and encrypts the registration code and stores it in a secure storage space.

In step S1040, the authentication server 124 sequentially passes through the application 122 and the application to be activated, and sends the registration information to the activation management application 112 in the terminal device. The activation management application 112 uses the trusted key to decrypt the registration information to obtain the registration code; and encrypts and stores the registration code in a secure storage space.

For the specific implementation process of step S1040, reference may be made to the related descriptions of the foregoing steps S830 and S840, which will not be repeated here.

When a user uses an application, the activation verification of the application will be triggered. Only when it is verified that the application activation is successful, the user can use the application; if the verification of the application activation fails, the application is not available to the user.

FIG. 11 shows a flowchart of a method 1100 for verifying application activation based on a trusted execution environment according to an embodiment of the present invention. The method 1100 is executed in the trusted execution environment of the terminal device, for example, executed by the activation management application 112 in the trusted execution environment. As shown in Figure 11, the method l loo starts with step smo.

In step smo, the trusted identity, the trusted key, and the registration code of the application to be verified are obtained. The registration code includes usage authority information and verification information, and the verification information is the use of the trusted key to the trusted identity, Use permission information to encrypt the generated ciphertext.

According to an embodiment, the activation verification application 112 obtains the trusted identity, the trusted key, and the registration code of the application to be verified from the secure storage space 111.

Subsequently, in step S1120, a trusted key is used to encrypt the trusted identity and usage authority information to generate a sixth ciphertext.

Subsequently, in step S1130, if the sixth ciphertext is consistent with the verification information, the registration code is sent to the application to be verified, so that the application determines whether the activation is successful according to whether the current use environment matches the use permission information.

For example, the use permission information includes effective time, expiration time, and available times. Accordingly, the current use environment of the application includes information such as time and used times. If the current time is within the range of effective time to expiration time, and the used times of the application are less than or equal to the available times, the current use environment matches the use permission information, and the application is successfully activated. Fig. 12 shows a schematic diagram of an application activation verification process based on a trusted execution environment according to an embodiment of the present invention. In FIG. 12, the secure storage space 111, the activation management application 112, and the second common application 116 are all located in the terminal device 110, the activation management application 112 is a trusted application in a trusted execution environment, and the second common application 116 is a rich execution environment Common applications in.

In step S1201, when the user uses the second common application 116, the second common application 116 initiates an activation verification request to the activation management application 112.

In steps S1202 and S1203, the activation management application 112 obtains the trusted identity ID, the trusted key IDkey, and the activation code ActiCode of the trusted execution environment from the secure storage space 111.

In step S 1204, the activation management application 112 verifies whether the trusted execution environment is successfully activated according to the trusted identity ID, the trusted key IDkey, and the activation code ActiCode. In the case that the trusted execution environment is successfully activated, step S 1205 is continued.

In steps S 1205 and S 1206, the activation management application 112 obtains the registration code License from the secure storage space 111. See Table 4. The License includes the effective time Stime2, the expiration time Etime2, the available times Times2, and the verification information HMAC (IDkey, ID + Stime2 + Etime2 + Times2).

In step S 1207, the activation management application 112 uses the trusted key IDkey to encrypt the trusted identity ID, the effective time Stime2, the expiration time Etime2, and the available times Times2 to generate a sixth ciphertext. If the sixth ciphertext is consistent with the verification information in the License, step S1208 is executed.

In step S 1208, the activation management application 112 sends the registration code to the second common application 116.

In step S 1209, the second common application 116 obtains the current use environment, and the current use environment includes the current time and the number of times the second common application 116 has been used. Read the effective time Stime2, the expiration time Etime2, and the available times Times2 in the registration code. Determine whether the current time is within the effective time Stime2~effective time Etime2, and whether the used times are less than or equal to the available times Times2. If the current time is within the time range from the effective time Stime2 to the expiration time Etime2, and the used times are less than or equal to the available times Times2, the second common application 116 is successfully activated.

The various technologies described here can be implemented in combination with hardware or software, or a combination of them. Therefore, the method and device of the present invention, or some aspects or parts of the method and device of the present invention may be embedded in a tangible medium, such as a removable hard disk, U disk, floppy disk, CD-ROM, or any other machine-readable storage medium In the form of program code (ie instructions) in, when the program is loaded into a machine such as a computer and executed by the machine, the machine becomes a device for practicing the present invention.

When the program code is executed on a programmable computer, the computing device generally includes a processor, Read storage medium (including volatile and non-volatile memory and/or storage element), at least one input device, and at least one output device. The memory is configured to store program code; the processor is configured to execute the application activation method based on the trusted execution environment of the present invention according to instructions in the program code stored in the memory.

By way of example and not limitation, readable media include readable storage media and communication media. The readable storage medium stores information such as computer readable instructions, data structures, program modules, or other data. Communication media generally embody computer-readable instructions, data structures, program modules, or other data by modulated data signals such as carrier waves or other transmission mechanisms, and include any information delivery media. Combinations of any of the above are also included in the scope of readable media.

In the instructions provided here, the algorithms and displays are not inherently related to any particular computer, virtual system or other equipment. Various general-purpose systems can also be used with the examples of the present invention. From the above description, the structure required to construct this type of system is obvious. In addition, the present invention is not directed to any specific programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of a specific language is for disclosing the best embodiment of the present invention.

In the instructions provided here, a lot of specific details are explained. However, it can be understood that the embodiments of the present invention can be practiced without these specific details. In some examples, well-known methods, structures and technologies are not shown in detail, so as not to obscure the understanding of this specification.

Similarly, it should be understood that in order to simplify the present disclosure and help understand one or more of the various aspects of the invention, in the above description of the exemplary embodiments of the present invention, the various features of the present invention are sometimes grouped together into a single embodiment. Figure, or its description. However, the disclosed method should not be interpreted as reflecting the following intention: That is, the claimed invention requires more features than the features explicitly recorded in each claim. More precisely, as reflected in the following claims, the inventive aspect lies in less than all the features of a single embodiment disclosed previously. Therefore, the claims following the specific embodiment are hereby explicitly incorporated into the specific embodiment, wherein each claim itself serves as a separate embodiment of the present invention.

Those skilled in the art should understand that the modules or units or components of the device in the example disclosed herein can be arranged in the device as described in this embodiment, or alternatively can be positioned differently from the device in this example In one or more devices. The modules in the preceding examples can be combined into one module or can be divided into multiple sub-modules.

Those skilled in the art can understand that it is possible to adaptively change the modules in the device in the embodiment and set them in one or more devices different from the embodiment. The modules or units or components in the embodiments can be combined into one module or unit or component, and in addition, they can be divided into multiple sub-modules or sub-units Or subcomponents. Except that at least some of such features and/or processes or units are mutually exclusive, any combination can be used to compare all features disclosed in this specification (including the accompanying claims, abstract and drawings) and any method or methods disclosed in this manner or All the processes or units of the equipment are combined. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

In addition, those skilled in the art can understand that although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features of different embodiments means that they are within the scope of the present invention. Within and form different embodiments. For example, in the following claims, any one of the claimed embodiments can be used in any combination.

In addition, some of the described embodiments are described herein as methods or combinations of method elements that can be implemented by a processor of a computer system or by other devices that perform the described functions. Therefore, a processor with the necessary instructions for implementing the method or method element forms a device for implementing the method or method element. In addition, the elements of the device embodiment described herein are examples of the device: The device is used to implement the function performed by the element for the purpose of implementing the invention.

As used herein, unless otherwise specified, the use of ordinal numbers "first", "second", "third", etc. to describe ordinary objects merely means different instances of similar objects, and is not intended to imply such The described objects must have a given order in terms of time, space, order, or in any other way.

Although the present invention has been described in terms of a limited number of embodiments, benefiting from the above description, those skilled in the art will understand that other embodiments can be envisaged within the scope of the invention thus described. In addition, it should be noted that the language used in this specification is mainly selected for readability and teaching purposes, not for explaining or limiting the subject of the present invention. Therefore, without departing from the scope and spirit of the appended claims, many modifications and changes are obvious to those of ordinary skill in the art. As for the scope of the present invention, the disclosure of the present invention is illustrative rather than restrictive, and the scope of the present invention is defined by the appended claims.

Claims

1. A method for activating a trusted execution environment, the trusted execution environment being deployed in a terminal device, the method including:

Send the terminal equipment identification to the server;

Receive activation information returned by the server, where the activation information includes an encrypted trusted identity, a trusted key, and an activation code, and the trusted identity and the trusted key correspond to the terminal device identity, so The activation code is generated according to the terminal device identification;

Decrypt the activation information to obtain a trusted identity, a trusted key, and an activation code;

The trusted identity, the trusted key, and the activation code are encrypted and stored in a secure storage space.

2. The method according to claim 1, wherein the activation information comprises a ciphertext generated by encrypting the trusted identity identifier, the trusted key, and the activation code ciphertext using a session key, and the activation The code ciphertext is a ciphertext generated by encrypting the activation code using the trusted key.

3. The method according to claim 2, wherein the step of decrypting the activation information to obtain a trusted identity identifier, a trusted key and an activation code comprises:

Decrypt the activation information by using the session key to obtain the trusted identity, the trusted key, and the ciphertext of the activation code;

Use the trusted key to decrypt the activation code cipher text to obtain the activation code.

4. The method according to claim 1, wherein after the step of decrypting the activation information, the method further comprises:

The activation code is verified according to the terminal device identifier, and after the activation code is verified, the trusted identity identifier, the trusted key and the activation code are encrypted and stored in a secure storage space.

5. The method according to claim 4, wherein the activation code includes use permission information and verification information of a trusted execution environment, and the verification information includes using the trusted key to verify the trusted identity The ciphertext generated by encrypting the identification, use authority information, and terminal device identification;

The step of verifying the activation code according to the terminal device identifier includes:

Encrypting the trusted identity identifier, use authority information, and terminal device identifier by using a trusted key to generate a first ciphertext;

If the first ciphertext is consistent with the verification information, the activation code verification is passed.

6. The method of claim 5, wherein the usage authority information includes effective time, expiration time, and available times.

7. The method according to claim 1, further comprising:

Generate an authentication code according to the terminal device identification;

The authentication code is sent to the server, so that the server verifies the authentication code, and after the authentication code is verified, an activation code is generated according to the terminal device identification.

8. The method according to claim 7, wherein the authentication code includes a preset key, a second ciphertext, and a first mapping value, and the second ciphertext is a pair of session key and A ciphertext generated by encrypting the terminal device identifier, where the first mapping value is a value obtained by mapping the session key and the terminal device identifier using a preset mapping function;

The server is suitable for verifying the authentication code according to the following method:

Use the preset key to decrypt the second ciphertext to obtain the session key and the terminal device identifier, and use the preset mapping function to calculate the session key and the terminal If the second mapping value of the device identifier is consistent with the first mapping value, the authentication code verification is passed.

9. The method of claim 1, executed by an activation management application in the trusted execution environment, and the secure storage space can only be accessed by the activation management application.

10. The method of claim 9, wherein the activation management application communicates with the server via an interface application located in a rich execution environment.

11. A method for activating a trusted execution environment, the trusted execution environment being deployed in a terminal device, the method comprising:

Receiving the terminal device identifier sent by the terminal device;

Generating a trusted identity identifier and a trusted key corresponding to the terminal device identifier, and generating an activation code according to the terminal device identifier;

Encrypting the trusted identity, the trusted key and the activation code to generate activation information;

The activation information is sent to the terminal device, so that the terminal device: decrypts the activation information to obtain a trusted identity, a trusted key, and an activation code, and transmits the trusted identity to The letter key and activation code are encrypted and stored in a secure storage space.

12. The method according to claim 11, wherein the activation information is generated according to the following steps: encrypting the activation code with the trusted key to generate an activation code ciphertext;

The session key is used to encrypt the trusted identity, the trusted key, and the cipher text of the activation code to generate activation

13. The method of claim 11, wherein the activation code includes a trusted execution environment usage authority letter Information and verification information, where the verification information includes a cipher text generated by encrypting the trusted identity identifier, usage authority information, and terminal device identifier using the trusted key.

14. The method of claim 13, wherein the usage authority information includes effective time, expiration time, and available times.

15. The method of claim 11, further comprising:

Receiving an authentication code sent by a terminal device, where the authentication code is generated according to the terminal device identifier;

Verify the authentication code;

After the authentication code is verified, an activation code is generated according to the terminal device identification.

16. The method according to claim 15, wherein the authentication code includes a preset key, a first ciphertext, and a first mapping value, and the first ciphertext is a pair of session key and A ciphertext generated by encrypting the terminal device identifier, where the first mapping value is a value obtained by mapping the session key and the terminal device identifier using a preset mapping function;

The step of verifying the authentication code includes:

Decrypt the first ciphertext by using the preset key to obtain the session key and the terminal device identifier;

The preset mapping function is used to calculate the second mapping value of the session key and the terminal device identifier; if the second mapping value is consistent with the first mapping value, the authentication code verification is passed.

17. A method for activation verification of a trusted execution environment, executed in a trusted execution environment of a terminal device, the method comprising:

Acquire a trusted identity, a trusted key, and an activation code of a trusted execution environment, where the activation code includes use permission information and verification information of the trusted execution environment, and the verification information includes using the trusted key Ciphertext generated by encrypting the trusted identity identifier, use authority information, and terminal device identifier;

Acquiring a terminal device identifier, encrypting the trusted identity identifier, use authority information, and terminal device identifier using a trusted key, to generate a first cipher text;

If the first ciphertext is consistent with the verification information, and the current use environment of the terminal device matches the use authority information, the trusted execution environment is successfully activated.

18. An application activation method based on a trusted execution environment, the trusted execution environment being deployed in a terminal device, the method including:

Send the trusted identity of the terminal device to the server:

Receive registration information returned by the server, where the registration information includes the available information corresponding to the trusted identity A registration code encrypted by a trust key, where the registration code is generated according to the trusted identity identifier;

Decrypt the registration information by using a trusted key to obtain a registration code;

The registration code is encrypted and stored in a safe storage space.

19. The method of claim 18, further comprising:

Verify whether the trusted execution environment is successfully activated;

In the case of successful activation of the trusted execution environment, the trusted identity of the terminal device is sent to the server.

20. The method according to claim 18, wherein, after the step of using a trusted key to decrypt the registration information, the method further comprises:

The registration code is verified according to the trusted identity, and after the verification of the registration code is passed, the registration code is encrypted and stored in a secure storage space.

21. The method according to claim 20, wherein the registration code includes usage authority information and verification information of the application to be activated, and the verification information includes using the trusted key to verify the trusted identity The ciphertext generated by encrypting the identifier and the usage authority information;

The step of verifying the registration code according to the trusted identity includes:

Use a trusted key to encrypt the trusted identity and use authority information to generate a first ciphertext; if the first ciphertext is consistent with the verification information, the registration code verification is passed.

22. The method of claim 21, wherein the usage authority information includes effective time, expiration time, and available times.

23. The method of claim 18, further comprising:

Generate an authentication code according to the trusted identity;

The authentication code is sent to the server, so that the server verifies the authentication code, and after the authentication code is verified, the registration code is generated according to the trusted identity.

24. The method according to claim 23, wherein the authentication code includes a preset key, a second cipher text, and a first mapping value, and the second cipher text is a trusted identity identification using the preset key Performing encryption on the generated ciphertext, where the first mapping value is a value obtained by mapping the trusted identity identifier using a preset mapping function;

Use the preset key to decrypt the second ciphertext to obtain the trusted identity, use the preset mapping function to calculate the second mapping value of the trusted identity, if the second If the mapping value is consistent with the first mapping value, the authentication code verification is passed.

25. The method of claim 18, executed by an activation management application in the trusted execution environment, the The secure storage space can only be accessed by the activation management application.

26. The method of claim 25, wherein the activation management application communicates with the server via the application to be activated.

27. An application activation method based on a trusted execution environment, the trusted execution environment being deployed in a terminal device, the method including:

Receive the trusted identity sent by the terminal device;

Generating a registration code according to the trusted identity;

Use the trusted key corresponding to the trusted identity to encrypt the registration code to generate registration information; send the registration information to the terminal device, so that the terminal device: uses a trusted key pair Decrypting the registration information to obtain a registration code; and encrypting and storing the registration code in a secure storage space.

28. The method of claim 27, wherein the registration code includes usage authority information and verification information of the application to be activated, and the verification information includes using the trusted key to verify the trusted identity The ciphertext generated by encrypting the identifier and the usage authority information.

29. The method of claim 28, wherein the usage authority information includes effective time, expiration time, and available times.

30. The method of claim 28, wherein the method is executed on a server, and the server includes an application server and an authentication server, the usage authority information is generated by the application server, and the verification The authentication information is generated by the authentication server.

31. The method of claim 27, further comprising:

Receiving an authentication code sent by a terminal device, where the authentication code is generated according to the trusted identity identifier;

Verify the authentication code;

After the authentication code is verified, a registration code is generated according to the trusted identity identifier.

32. The method according to claim 31, wherein the authentication code includes a preset key, a first ciphertext, and a first mapping value, and the first ciphertext is a trusted identity identification using the preset key Performing encryption on the generated ciphertext, where the first mapping value is a value obtained by mapping the trusted identity identifier using a preset mapping function;

The step of verifying the authentication code includes:

Decrypt the first ciphertext by using the preset key to obtain the trusted identity;

Using the preset mapping function to calculate the second mapping value of the trusted identity;

If the second mapping value is consistent with the first mapping value, the authentication code verification is passed.

33. An application activation verification method based on a trusted execution environment, which executes in the trusted execution environment of a terminal device OK, the method includes:

Obtain a trusted identity, a trusted key, and a registration code of the application to be verified, where the registration code includes usage authority information and verification information, and the verification information is that the trusted key is used to verify the trusted The ciphertext generated by encrypting the identity identification and the use authority information;

Use the trusted key to encrypt the trusted identity and use authority information to generate a first ciphertext; if the first ciphertext is consistent with the verification information, the registration code is sent to The application to be verified, so that the application determines whether it is successfully activated according to whether the current use environment matches the use permission information.

34. A terminal device on which a trusted execution environment is deployed,

The trusted execution environment includes an activation management application, and the activation management application is adapted to execute the method according to any one of claims 1- 10, 17, 18-26, and 33.

35. A server, including:

At least one processor; and

A memory storing program instructions, where the program instructions are configured to be executed by the at least one processor, and the program instructions include instructions for executing any one of claims 11-16 and 27-32. Instructions for the described method.

36. An application activation system based on a trusted execution environment, including:

The terminal device according to claim 34; and

The server according to claim 35.