CN111625829A - Application activation method and device based on trusted execution environment - Google Patents

Abstract

The invention discloses a method for activating a trusted execution environment. The trusted execution environment is deployed in a terminal device. The method includes: sending an identification of the terminal device to a server; and receiving activation information returned by the server, where the activation information includes encrypted The trusted identity, trusted key and activation code are corresponding to the terminal equipment identification, and the activation code is generated according to the terminal equipment identification; the activation information is decrypted to obtain the trusted identification , trusted keys and activation codes; encrypted storage of trusted identities, trusted keys and activation codes in a secure storage space. The invention also discloses an activation verification method of a trusted execution environment, an application activation and activation verification method based on the trusted execution environment, and a corresponding device.

Description

Application activation method and device based on trusted execution environment

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, there needs to be a way to prevent the software from being cracked and misappropriated, so as to protect the interests of the software developers. At present, the software is usually protected by means of a registration code, that is, a user first downloads and installs a trial version of the software, and then activates the software by applying for a registration code to the server. After that, 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, so that the software installed on other devices can be illegally cracked. In addition, the content of the registration code file may be tampered with by the user to illegally extend the number of times or the validity period of the software.

2. The registration code file is not bound to the device, so the registration code file can be used in different devices, and the software installed on other devices can be 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, there is a need to provide a more secure software activation method.

SUMMARY OF THE INVENTION

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

According to a first aspect of the present invention, a method for activating a trusted execution environment is provided, where the trusted execution environment is deployed in a terminal device, and the method includes: sending an identifier of the terminal device to a server; The activation information includes the encrypted trusted identity identifier, trusted key and activation code, the trusted identity identifier and trusted key correspond to the terminal device identifier, and the activation code is based on the The terminal device identification is generated; the activation information is decrypted to obtain a trusted identification, a trusted key and an activation code; the trusted identification, trusted key and activation code are encrypted and stored 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 generating an activation code according to the terminal device identifier; encrypting the trusted identity identifier, 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 converts the trusted identity, trusted Keys and activation codes are encrypted and stored in a secure storage space.

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

According to a fourth aspect of the present invention, there is provided an application activation method based on a trusted execution environment, where 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 Terminal: receive the registration information returned by the server, where the registration information includes a registration code encrypted with the 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, there is provided an application activation method based on a trusted execution environment, where 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 all 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, there is provided an application activation verification method based on a trusted execution environment, executed in a trusted execution environment of a terminal device, the method comprising: acquiring a trusted identity identifier, a trusted key and The registration code of the application to be verified, the registration code includes use authority information and verification information, and the verification information is generated by encrypting the trusted identity identifier and the use authority information with the trusted key ciphertext; use the trusted key to encrypt the trusted identity identifier and use authority information to generate a first ciphertext; if the first ciphertext is consistent with the verification information, register the The code is sent to the application to be verified, so that the application determines whether the activation is successful according to whether the current usage environment matches the usage permission information.

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

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

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

The present invention provides an application activation scheme based on a trusted execution environment. A Trusted Execution Environment is an independent, trusted environment with an isolated hardware environment and an independent operating system that can be used to store, process, and protect sensitive data. In the technical solution of the present invention, first, the trusted execution environment in the terminal device is activated, and on the basis that 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 authentication service to keep other applications safe. 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, and the data in the secure storage space can only be read by the activation management application in the trusted execution environment, ensuring its It will not be illegally obtained and tampered with.

In the process of activating the trusted execution environment, the server generates a trusted identity and a trusted key of the terminal device. Then, the trusted key is applied to the activation code of the trusted execution environment and the encrypted transmission process of the registration code of the application. The trusted key is only transmitted once between the terminal device and the server, that is, during and only in the process of activating the trusted execution environment, the server encrypts and transmits the generated trusted key to the terminal device, and then encrypts and transmits the generated trusted key to the terminal device. During the activation of the application by the 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 to Obtain the registration code, 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-replicability of the activation code and registration code of each terminal device. If the activation code and registration code are maliciously tampered with, the trusted execution environment of the terminal device and the activation verification of 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 solutions of the present invention, in order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand , the following specific embodiments of the present invention are given.

Description of drawings

To achieve the above and related objects, certain illustrative aspects are described herein in conjunction with the following description and drawings, which are indicative of the various ways in which the principles disclosed herein may be practiced, and all aspects and their equivalents are intended to be within the scope of the claimed subject matter. The above and other objects, features and advantages of the present disclosure will become more apparent by reading the following detailed description in conjunction with the accompanying drawings. Throughout this disclosure, the same reference numbers 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;

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 an 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;

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 a trusted execution environment-based application activation method 800 (terminal device side) 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;

10 shows a flowchart of a trusted execution environment-based application activation method 1000 (server side) according to an embodiment of the present invention;

FIG. 11 shows a flowchart of a method 1100 for application activation verification based on a trusted execution environment according to an embodiment of the present invention; 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 ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be more thoroughly understood, and will fully convey the scope of the present disclosure to those skilled in the art.

The present invention provides an application activation scheme based on a trusted execution environment. In the technical solution of the present invention, first, the trusted execution environment in the terminal device is activated, and on the basis that 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 authentication service to keep other applications safe.

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 can understand that in practice, the system 100 may include any number of terminal devices 110 and servers 120 , the present invention does not limit the number of terminal devices 110 and servers 120 included in the system 100 .

The terminal device 110 can 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 , the terminal device 110 is deployed with a Trusted Execution Environment (Trusted Execution Environment, TEE for short) and a Rich Execution Environment (Rich Execution Environment, REE for short). The trusted execution environment and the rich execution environment have mutually isolated hardware and independent operating systems, and are used to meet the running requirements of applications with different security levels. The hardware isolation of the trusted execution environment and the rich execution environment can be implemented by, for example, the security extension technology of ARM TrustZone or C-SKY, but is not limited thereto.

The operating system of the rich execution environment can be general-purpose operating systems such as Android, iOS, and RTOS real-time operating systems. Common applications that do not require high security, such as instant messaging, photography, and weather queries, can run on the operating system. The operating system of the trusted execution environment is usually a closed and relatively simple security operating system, on which trusted applications with high security requirements are run, such as fingerprint recognition, identity authentication, electronic payment, and smart locks. Wait. Trusted applications in the trusted execution environment can be invoked by ordinary applications in the rich execution environment to implement corresponding functions. Trusted applications cannot directly communicate with the outside world (such as servers, other terminal devices, users, etc.), but need to use ordinary applications in the rich execution environment as communication relays, that is, trusted applications in the trusted execution environment pass through the rich execution environment. Common applications in to communicate with the outside world.

The server 120 may be any device used to provide the terminal device 110 with a trusted execution environment online activation service, such as a physical server, or a computing instance deployed in the physical server, but not limited to this. The server 120 is used to provide the terminal device 110 with an online activation service of the 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 the interface application 113 deployed in the rich execution environment for activating 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 identification, generates a trusted identification and a trusted key of the terminal, and stores the trusted identification and trusted key in association with the identification of the terminal. The trusted identity identifier is a character string that can represent the uniqueness of the device, which is used to uniquely identify the terminal device 110, and has security properties that cannot be tampered with, cannot be forged, and are globally unique. The trusted key is a character string derived through a specific algorithm according to the trusted identity, and is used to encrypt key information related to the terminal device 110 . The server 120 generates activation information after encrypting the trusted identity identifier, the trusted key and the activation code, 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, obtains the trusted ID, trusted key and activation code, and then encrypts and stores the trusted ID, trusted key and activation code in the secure storage space 111 . The secure storage space 111 is a designated space for storing files, and the files are encrypted with a trusted key and stored in this location. In an embodiment of the present invention, the secure storage space 111 can and only be accessed by the activation management application 112 . After the trusted identity identifier, the trusted key and the activation code are encrypted and stored in the secure storage space 111, the trusted execution environment activation of the terminal device 110 is completed.

Common applications in the rich execution environment can call trusted applications in the trusted execution environment. When the trusted application is invoked, the invoked trusted application will further invoke the activation management application 112 to trigger activation verification of the trusted execution environment. The activation management application 112 reads the trusted ID, trusted key and activation code from the secure storage space 111, and verifies whether the trusted execution environment is successfully activated according to the trusted ID, trusted key and activation code, and then, Return the verification result to the trusted application called by the normal application. If the verification and activation are successful, the called trusted application executes the calling of the common application, and returns the calling result to the common 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 needs to pay for the purchase, the first common application 114 invokes the first trusted application 115 to implement the electronic payment function. After the first trusted application 115 is invoked, the activation management application 112 is triggered to perform activation verification of the trusted execution environment. The activation management application 112 reads the trusted ID, trusted key and activation code from the secure storage space 111, verifies whether the trusted execution environment is successfully activated according to the trusted ID, trusted key and activation code, The verification result is returned to the first trusted application. If the verification and activation are successful, the first trusted application 115 executes the call of the first common application 114 to realize the electronic payment function, and returns the call result (whether the payment is successful) to the first common application 114 .

On the basis that the trusted execution environment has been activated, the trusted execution environment may provide application 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. On the basis that 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 method and data calls to the second common application 116 , and can generate usage permission information (eg, effective time, expiry time, available times, etc.) for activating the second common application 116 . The authentication server 124 is used for verifying the identity of the terminal device 110, generating verification information according to the use authority information, and encrypting the use authority information and the verification information, and the like.

Specifically, the second common application 116 triggers the activation management application 112 to verify whether the trusted execution environment is successfully activated, and if 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 usage authority information of the second common application 116 , and sends the usage authority information to the authentication server 124 . The authentication server 124 generates verification information according to the use authority information and the trusted identity, combines the use authority 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 performed in a trusted execution environment of a terminal device (eg, the aforementioned terminal device 110 ), eg, by the activation management application 112 in the trusted execution environment. As shown in FIG. 3, the method 300 begins at step S310.

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

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

Specifically, step S310 is performed by an activation management application in a trusted execution environment. The activation management application 112 cannot communicate with the server directly, 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 can be sent to the server together, so that the server can verify the authentication code. After the code verification is passed, the activation code is generated according to the terminal device identification.

According to an embodiment, the authentication code includes a preset key, a first ciphertext, and a first mapping value, wherein the first ciphertext is a cipher generated by encrypting the session key and the terminal device identifier with the preset key. In the text, 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 end device, eg, 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 (Token) for this communication, where the token includes 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, the use of the preset key , preset key type, 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, which is not limited in the present invention. 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 thereto.

After the authentication code is generated, the authentication code and the terminal device identification are sent to the server together, so that the server can verify the authentication code, recover the session key from it, and ensure that the authentication code and the terminal device identification are not changed during the transmission process. interception or malicious tampering. According to an embodiment, 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 ciphertext in the authentication code to obtain the session key and the terminal device identification. Then, a 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 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 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 the fields of the authentication code and transmitted to the server together with the authentication code; and so on. The present invention does not limit the specific method for synchronizing the algorithm parameters between the terminal device and the server.

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

Table 1

In Table 1, the preset key is Provisioning Key1, and the first ciphertext is Provisioning_Key_Encrypt(Session Key+Dev_FP), that is, the first ciphertext is the use of the preset key Provisioning Key1 to identify the session key Session Key and the terminal device identification The ciphertext obtained by Dev_FP encryption. 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, the preset password key usage, preset key type, 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 identifier 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 first ciphertext Provisioning_Key_Encrypt (Session Key+Dev_FP) is decrypted by using Provisioning Key1 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, then AuthCode1 is verified successfully.

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

Trusted identities and trusted keys are generated by the server. The server generates a trusted ID and a trusted key, and stores the trusted ID and trusted key in association with the terminal device ID. A trusted identity identifier is a string that can represent the uniqueness of a device and is used to uniquely identify a terminal device, and it has the security attributes of untamperable, unforgeable, and globally unique. The trusted key is a character string derived by a specific algorithm according to the trusted identity, and 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 usage authority information and verification information of the trusted execution environment.

The usage permission information of the trusted execution environment is used to mark the usage permission of the trusted execution environment. The usage authority information may include, for example, an effective time, an expiry time, and available times, etc., but is not limited thereto. When the use authority information includes the effective time and the expiry time, the terminal device can normally use the trusted execution environment only within the time range from the effective time to the expiry time. The execution environment is inactive and the trusted execution environment is not available. When the usage authority information includes the available times, the terminal device can only call the TEE within the available times. If the terminal device calls the TEE for the available times, the TEE will be in an inactive state and can The letter execution environment is not available. Those skilled in the art can understand that the use permission information can be configured, which can include at least one of the effective time, the expiry time, and the available times, and can also include other information except the effective time, the expiry time, and the available times. The invention does not limit the specific content included in the use authority 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 ciphertext generated by encrypting the trusted identity identifier, use authority information, and terminal device identifier with 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, 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 use right information includes the effective time Stime1, the expiry time Etime1 and the available times Times1. The verification information is HMAC(IDkey,Dev_FP+ID+Stime1+Etime1+Times1), that is, the verification information is based on the HMAC algorithm, using the trusted key IDkey to identify the terminal equipment Dev_FP, trusted identity ID, effective time Stime1 , the expiration time Etime1 and the available times Times1 to encrypt the message digest 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 the trusted key IDkey, for 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. are not restricted.

In step S320, the activation information includes an encrypted trusted identity identifier, a trusted key and an activation code. According to an embodiment, the activation information may be generated according to the following steps: encrypting the activation code with a trusted key to generate an activation code ciphertext; 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 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, The session key Session Key can be implied in the authentication code AuthCode1 and passed to the server; etc. The present invention does not limit the generation of the session key and the transmission 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 may be any encryption algorithm, which is not limited in the present invention.

Taking Table 1 and Table 2 as examples, the generation steps of the activation information are as follows: first, use the trusted key IDkey to encrypt the activation code ActiCode, and generate the activation code ciphertext ActiCode'. Then, use the session key Session Key determined from the authentication code AuthCode1 to encrypt the trusted identity ID, trusted key IDkey, and 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 identifier, a trusted key and an activation code.

The process of decrypting the activation information is opposite to the process of encrypting and generating the activation information by the server. According to an embodiment, the activation information is decrypted according to the following steps: first, the activation information is decrypted by using the session key to obtain the trusted identity identifier, the trusted key and the activation code ciphertext; then, the trusted encryption is used to decrypt the activation information. The key decrypts the activation code ciphertext to obtain the activation code.

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

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

In step 340, the trusted identity identifier, 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 in the secure storage space will not be illegally obtained and tampered with.

According to an embodiment, after obtaining the trusted ID, trusted key and activation code in step S330, instead of directly encrypting and storing the trusted ID, trusted key and activation code in the 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 verification is passed, the trusted identity identifier, the trusted key and the activation code are encrypted and stored in a 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, use authority information, and terminal device identifier to generate a second ciphertext; if the second ciphertext and the activation code If the verification information 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 identifier Dev_FP (for example, through the data interface provided by the manufacturer of the terminal device). Based on the HMAC algorithm, the trusted key IDkey is used to encrypt the terminal device identifier Dev_FP, the trusted identity identifier ID, the valid time Stime1, the invalidation time Etime1 and the available times Times1 to generate the second ciphertext. If the second ciphertext is consistent with the verification information in the activation code, the activation code verification is passed. Otherwise, the verification fails.

After the trusted identity identifier, trusted key and activation code are encrypted and stored in the secure storage space 111, the trusted execution environment activation of the terminal device is completed. The trusted identity identifier, 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 the trusted execution environment, and the interface application 113 is a common application in the rich execution environment. .

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

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 there is no ActiCode stored in the secure storage space 111 or the activation management application 112 fails to verify the ActiCode, 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 performed.

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 the authentication code AuthCode1 according to the terminal device identifier Dev_FP. As shown in the aforementioned Table 1, AuthCode1 includes the preset key Provisioning Key1, the first ciphertext Provisioning_Key_Encrypt (Session Key+Dev_FP), and the first ciphertext Provisioning_Key_Encrypt (Session Key+Dev_FP), A mapping value Hash_Sha256 (Session 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 sends the terminal device identification Dev_FP and the authentication code AuthCode1 to the server 120 .

In step S410, the server 120 verifies the authentication code AuthCode1: first, reads the provisioning key Provisioning Key1 from the authentication code AuthCode1. Then, the first ciphertext Provisioning_Key_Encrypt (Session Key+Dev_FP) is decrypted by using Provisioning Key1 to recover the session key SessionKey. 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, then AuthCode1 is verified successfully. Subsequently, step S411 is performed.

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

In step S412, the server 120 generates an activation code ActiCode according to the terminal device identifier Dev_FP. As shown in Table 2, the ActiCode includes the effective time Stime1, the expiry time Etime1, the available times Times1 and the verification information HMAC(IDkey,Dev_FP+ID+Stime1 +Etime1+Times1). 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, trusted key IDkey, and 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 Session Key to decrypt the activation information to obtain the trusted identity ID, trusted key IDkey, and activation code ciphertext ActiCode'. Then, use the trusted key IDkey to decrypt the activation code ciphertext ActiCode' to obtain the activation code ActiCode.

In step S416, the activation management application 112 acquires the terminal device identifier Dev_FP through the data interface provided by the manufacturer of the terminal device. Based on the HMAC algorithm, the trusted key IDkey is used to encrypt the terminal device identifier Dev_FP, the trusted identity identifier ID, the valid time Stime1, the invalidation time Etime1 and the available times Times1 to generate the second ciphertext. If the second ciphertext is consistent with the verification information in the activation code, the activation code verification is passed, and step S417 is executed.

In steps S417 and S418, the activation management application 112 encrypts and stores the trusted identity ID, trusted key IDkey and 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 the 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. The 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 begins at step S510.

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

Since the activation management application 112 cannot communicate with the server directly, but needs to communicate with the server via the interface application 113 in the rich execution environment, 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, an 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 verification of the authentication code is passed, step S520 is performed to generate an activation code according to the terminal device identifier.

According to an embodiment, the authentication code includes a preset key, a first ciphertext, and a first mapping value, wherein the first ciphertext is a cipher generated by encrypting the session key and the terminal device identifier with the preset key. In the text, 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 ciphertext in the authentication code to obtain the session key and terminal equipment identification. Then, a 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 consistent with the first mapping value in the authentication code, the authentication code verification is passed.

For the specific implementation steps of the generation and verification of the authentication code, reference may be made to the relevant description of the foregoing 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 the security properties of being untamperable, unforgeable, and globally unique. A trusted key is a key corresponding to a trusted identity, which is used to encrypt key information. The server can generate the trusted identity mark and the trusted key according to any algorithm, and the present invention does not limit the specific algorithm used to generate the trusted identity mark and the trusted key. After the trusted identity and the trusted key are generated, the trusted identity and the trusted key are stored in association.

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 usage authority information and verification information of the trusted execution environment.

The usage permission information of the trusted execution environment is used to mark the usage permission of the trusted execution environment. The usage authority information may include, for example, an effective time, an expiry time, and available times, etc., but is not limited thereto.

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 ciphertext generated by encrypting the trusted identity identifier, use authority information, and terminal device identifier with 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, an HMAC algorithm, but is not limited thereto. For an example of the activation code ActiCode, reference may be made to the foregoing Table 2, which will not be repeated here.

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

According to an embodiment, the activation code is encrypted with a trusted key to generate the activation code ciphertext; the trusted identity identifier, the trusted key and the activation code ciphertext are encrypted with the session key to generate the activation information . For the specific steps of generating the activation information, reference may be made to the foregoing description of step S320, which is not 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 identifier, trusted key and activation code, and sends the trusted identity identifier, trusted key And the activation code is 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 will not be repeated here.

Common applications in the rich execution environment can call trusted applications in the trusted execution environment. When the trusted application is invoked, the invoked trusted application will further invoke the activation management application 112 to trigger activation verification of the trusted execution environment.

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. The method 600 is performed in the trusted execution environment of the terminal device, eg, by the activation management application 112 in the trusted execution environment. As shown in FIG. 6, the method 600 begins at step S610.

In step S610, obtain a trusted identity identifier, a trusted key, and an activation code of the trusted execution environment, where the activation code includes the use authority information and verification information of the trusted execution environment, and the verification information includes the use of a trusted key pair The ciphertext generated by the encryption of the trusted identity identifier, use permission 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 use authority information. For example, as shown in Table 2, the activation code ActiCode includes three items of use authority information: effective time Stime1, expiry time Etime1 and available times Times1, and verification information HMAC(IDkey,Dev_FP+ID +Stime1+Etime1+Times1). The verification information is a message digest generated by encrypting the terminal device identifier Dev_FP, trusted identity identifier ID, effective time Stime1, expiry time Etime1 and available times Times1 based on the HMAC algorithm using the trusted key IDkey.

Then, in step S620, the terminal device identification is obtained, and the trusted identification, usage authority information, and terminal device identification are encrypted with a trusted key to generate a third ciphertext.

According to an embodiment, the terminal equipment identifier Dev_FP is obtained through the data interface provided by the manufacturer of the terminal equipment, and based on the HMAC algorithm, the trusted identifier ID, the effective time Stime1, the expiry time Etime1, and the available times are determined by using the trusted key IDkey. Times1 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 successfully activated.

For example, the use right information includes the effective time, the expiry time, and the available times. Correspondingly, the current use environment of the terminal device includes information such as time, used times, and the like. If the current time of the terminal device is within the range from the effective time to the expiry time, and the used times is less than or equal to the available times, the current use environment of the terminal device matches the use permission 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 the rich execution environment.

In step S701 , the first common 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 includes effective time Stime1, expiry time Etime1, available times Times1 and verification information HMAC (IDkey, Dev_FP+ID+Stime1+Etime1+Times1).

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, valid time Stime1, invalidation time Etime1, available times Times1 and terminal device ID Dev_FP to generate a third ciphertext. If the third ciphertext 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 calling result to the first common application 114 .

On the basis that the trusted execution environment has been activated, the trusted execution environment may provide application 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 activating an application based on a trusted execution environment according to an embodiment of the present invention. The method 800 is performed in the trusted execution environment of the terminal device, eg, by the activation management application 112 in the trusted execution environment. The method 200 may be used to activate a generic application in a rich execution environment, such as the second generic application 116 shown in FIG. 2 . As shown in FIG. 8, the method 800 begins 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 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 (eg, 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; if the trusted execution environment is successfully activated, the trusted identity of the terminal device is sent to the server. to the server.

Specifically, the steps shown in the foregoing method 600 can be used to verify whether the trusted execution environment is successfully activated. 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 trusted execution environment fails to be activated, the trusted execution environment is unavailable. In this case, 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 an embodiment, in step S810, in addition to sending the trusted identity to the server, an authentication code is also generated according to the trusted identity, and the authentication code and the trusted identity are sent to the server, so that the server can verify the The authentication code is verified, and after the authentication code verification is passed, the registration code is generated according to the trusted identity identifier.

According to an embodiment, the authentication code includes a preset key, a fourth ciphertext, and a third mapping value, wherein the fourth ciphertext is a ciphertext generated by encrypting the trusted identity with the preset key, and the third The three mapping values are values obtained by using a preset mapping function to map the trusted identity 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. According to an embodiment, when the activation management application 112 communicates with the server, the activation management application 112 will generate a token (Token) for this communication, where the token includes 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, the use of the preset key , preset key type, 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, which is not limited in the present invention. For example, the encryption algorithm used to generate the fourth ciphertext may be the AES encryption algorithm, and the mapping function used to generate the third mapping value may be a hash algorithm, but is not limited thereto.

After the authentication code is generated, the authentication code and the trusted identity identifier are sent to the server together, so that the server can verify the authentication code and ensure that the authentication code and the trusted identity identifier have not been tampered with during the transmission process. 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 ciphertext to obtain the trusted identity, and use the preset mapping function to calculate the fourth mapping value of the trusted identity. The four mapping values are 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

Preset key Fourth ciphertext third map value Provisioning Key2 Provisioning_Key_Encrypt(ID) Hash_Sha256(ID)

In Table 3, the preset key is Provisioning Key2, and the fourth ciphertext is Provisioning_Key_Encrypt(ID), that is, the fourth ciphertext is the ciphertext obtained by encrypting the trusted identity ID by using the preset key Provisioning Key2 . The third mapping value is Hash_Sha256(ID), that is, the third mapping value is the hash value of the trusted identity ID calculated by 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 ID of the activation management application 112, the version number of the activation management application 112, the preset password key usage, preset key type, 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. Then, use Provisioning Key2 to decrypt the fourth ciphertext Provisioning_Key_Encrypt(ID) 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 verification of AuthCode2 is successful.

Subsequently, in step S820, the registration information returned by the server is received, 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.

The registration code is generated according to the trusted identity, and is 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, an effective time, an expiry time, and available times, etc., but is not limited thereto. When the use permission information includes the effective time and the expiry time, the user can use the application normally only within the time range from the effective time to the expiry time, and the application is unavailable outside the time range from the effective time to the expiry time. When the usage permission information includes the available times, the user can only use the application within the available times, and 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 use permission information can be configured, which can include at least one of the effective time, the expiry time, and the available times, and can also include other information except the effective time, the expiry time, and the available times. The invention does not limit the specific content included in the usage authority 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 an embodiment, the verification information includes a ciphertext generated by encrypting the trusted identity identifier and the usage authority information with 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, 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 permission information of the application includes the effective time Stime2, the expiry 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 the trusted key IDkey to identify the trusted identity ID, valid time Stime2, invalidation 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 identifier. 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 the method 800 is slightly different from the process of encrypting the activation code to generate the activation information in the method 300 . In method 300, the activation code is double-encrypted by the trusted key and the session key; in 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 together with the activation code. In order to ensure that the trusted key is not intercepted and tampered with, after the activation code is encrypted with the trusted key, the session key needs to be used to encrypt the trusted key, so that the trusted key is invisible to the outside world. In method 800, the trusted key is not transmitted, but is only stored in the terminal device and the server respectively. 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 using the trusted key to perform single encryption on the registration code, and there is no need to use the session key for secondary encryption.

Subsequently, in step S830, the registration information is decrypted by using the trusted key to obtain the registration code.

Then, 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 the secure storage space will not be illegally obtained and tampered with.

According to an embodiment, after obtaining the registration code in step S830, instead of directly encrypting the registration code and storing it in the secure storage space, the registration code is first verified according to the trusted identity identifier, so as to ensure that the registration information is stored on the server and the terminal device. The transmission process has not been illegally tampered with. After the registration code is verified, the registration code is encrypted and stored in a safe storage space.

According to an embodiment, the registration code can be verified according to the following steps: using a trusted key to encrypt the trusted identity identifier and use authority information to generate a fifth ciphertext; if the verification between the fifth ciphertext and 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, and use the trusted key IDkey to verify the trusted identity ID, valid time Stime2, invalidation time Etime2 and available times Times2 based on the HMAC algorithm. Encrypt to generate the fifth ciphertext. If the fifth ciphertext 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 the trusted execution environment, and the second common application 116 is a trusted execution environment in the rich execution environment. Application to be activated. The application server 122 and the authentication server 124 are located on the server. The application server 122 is configured to provide methods and data calls to the second common application 116, and generate usage permission information (eg, effective time, expiry time, available times, etc.) of the second common application 116. The authentication server 124 is used for verifying the identity of the terminal device 110 and encrypting related data.

In step S901, the second common 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 ID and 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 ciphertext Provisioning_Key_Encrypt(ID) and the third mapping value Hash_Sha256(ID).

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

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

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

In step S908, the authentication server 124 verifies the authentication code AuthCode2: first, reads the provisioning key Provisioning Key2 from the authentication code AuthCode2. Then, use Provisioning Key2 to decrypt the fourth ciphertext Provisioning_Key_Encrypt(ID) 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 verification of AuthCode2 is successful.

In step S909 , the authentication server 124 returns the result that the authentication code AuthCode2 is successfully verified to the application server 122 .

In step S910, the application server 122 generates usage authority information of the second common application 116, see Table 4, and the usage authority information includes the effective time Stime2, the expiry 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, see Table 4, and the verification information is HMAC(IDkey, ID+Stime2+Etime2+Times2). Then, the use authority information and the verification information are combined to form a registration code License. Find the trusted key IDkey corresponding to the trusted identity ID, use the IDkey to encrypt the license, and generate registration information.

In steps S913 to S915, the authentication server 124 sends the registration information to the activation management application 112 via the application server 122 and the second common application 116 in sequence.

In step S916, the activation management application 112 uses the trusted key IDkey to decrypt the registration information to obtain the registration code License. The trusted identity identifier ID, the valid time Stime2, the invalidation time Etime2 and the available times Times2 are encrypted by using the trusted key IDkey 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 to the second ordinary application 116 the result of the successful activation of the second ordinary application 116 .

FIG. 10 shows a flowchart of an application activation method 1000 based on a trusted execution environment according to an embodiment of the present invention. The method 100 is executed in the server (such as the server 120 shown in FIG. 2 ), which corresponds to the aforementioned method 800 executed in the terminal device, and is suitable for the application to be activated (such as the second common application 116 shown in FIG. 2 ). ) to activate.

According to an embodiment, the server further includes an application server (such as the application server 122 shown in FIG. 2 ) and an authentication server (such as the authentication server 124 shown in FIG. 2 ), and the application server and the authentication server divide labor Collaborate to enable trusted execution environment-based application activation. The application server can communicate directly with the application to be activated to provide methods and data calls to the application to be activated, and to generate usage permission information of the application to be activated (such as effective time, expiry time, available times, etc.). The authentication server usually does not communicate directly with the application to be activated, and is used for verifying the identity of the terminal device 110 and encrypting related data.

As shown in FIG. 10, the method 1000 begins at step S1010.

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

The trusted identity is stored in the secure storage space 111 of the terminal device, and 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 it to the application server through the application to be activated. Correspondingly, the application server receives the trusted identity identifier sent by the application to be activated.

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

According to an embodiment, after receiving the trusted identity identifier and authentication code sent by the second common application 116, the application server 122 forwards the trusted identity identifier and 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 will not be repeated here.

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

According to an embodiment, the registration code includes usage permission information and verification information of the application to be activated, wherein the usage permission information is used to mark the usage permission of the application, which may include, for example, an effective time, an expiry time, the number of times of availability, etc., But 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 ciphertext generated by encrypting the trusted identity identifier and the usage authority information with a trusted key.

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

Then, in step S1030, the registration code is encrypted by using the trusted key corresponding to the trusted identity identifier 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: uses a trusted key to decrypt the registration information to obtain a registration code; and encrypts and stores the registration code in a secure storage space.

In step S1040, the authentication server 124 sends the registration information to the activation management application 112 in the terminal device through the application terminal 122 and the application to be activated in sequence. The activation management application 112 decrypts the registration information by using the trusted key 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 relevant descriptions of the foregoing steps S830 and S840, which will not be repeated here.

When the user uses an application, the activation verification of the application will be triggered. The user can use the application only when it is verified that the activation of the application is successful; if the verification of the activation of the application fails, the application is unavailable to the user.

FIG. 11 shows a flowchart of a method 1100 for application activation verification based on a trusted execution environment according to an embodiment of the present invention. The method 1100 is performed in the trusted execution environment of the terminal device, eg, by the activation management application 112 in the trusted execution environment. As shown in FIG. 11, the method 1100 begins at step S1110.

In step S1110, a trusted identity identifier, a trusted key, and a registration code of an application to be verified are obtained, where the registration code includes use authority information and verification information, and the verification information is to use a trusted key to pair the trusted identifier, The ciphertext generated by encryption with permission information.

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

Subsequently, in step S1120, the trusted identity identifier and the use authority information are encrypted by using the trusted key 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 can determine whether it is successfully activated according to whether the current usage environment matches the usage permission information.

For example, the use permission information includes the effective time, the expiry time, and the available times, and accordingly, the current use environment of the application includes information such as time, used times, and the like. If the current time is within the range from the effective time to the expiry time, and the number of times the application has been used is less than or equal to the number of times the application is available, the current usage environment matches the usage 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 the 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 S1204, 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. If the trusted execution environment is successfully activated, step S1205 is continued.

In steps S1205 and S1206 , the activation management application 112 acquires the registration code License from the secure storage space 111 . Referring to Table 4, the license includes the effective time Stime2, the expiry time Etime2, the available times Times2 and the check information HMAC (IDkey, ID+Stime2+Etime2+Times2).

In step S1207, the activation management application 112 encrypts the trusted identity ID, the effective time Stime2, the expiry time Etime2 and the available times Times2 by using the trusted key IDkey to generate a sixth ciphertext. If the sixth ciphertext is consistent with the verification information in the License, step S1208 is executed.

In step S1208 , the activation management application 112 sends the registration code to the second normal application 116 .

In step S1209, the second common application 116 acquires the current usage environment, where the current usage environment includes the current time and the number of times the second common application 116 has been used. Read the effective time Stime2, the expiry time Etime2, and the available times Times2 in the registration code. Determine whether the current time is within the time range from the effective time Stime2 to the expiry time Etime2, and whether the used times is 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 expiry time Etime2, and the used times is less than or equal to the available times Times2, the second common application 116 is successfully activated.

The various techniques described herein can be implemented in conjunction with hardware or software, or a combination thereof. Thus, the method and apparatus of the present invention, or certain aspects or portions of the method and apparatus of the present invention, may take the form of an embedded tangible medium, such as a removable hard disk, a USB stick, a floppy disk, a CD-ROM, or any other machine-readable storage medium. in the form of program code (ie, instructions) that, when the program is loaded into a machine, such as a computer, and executed by the machine, the machine becomes an apparatus for practicing the invention.

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

By way of example and not limitation, readable media include readable storage media and communication media. Readable storage media store information such as computer readable instructions, data structures, program modules or other data. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. Combinations of any of the above are also included within the scope of readable media.

In the specification provided herein, the algorithms and displays are not inherently related to any particular computer, virtual system, or other device. Various general purpose systems may also be used with examples of the present invention. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not directed to any particular programming language. It is to be understood that various programming languages may be used to implement the inventions described herein, and that the descriptions of specific languages above are intended to disclose the best mode for carrying out the invention.

In the description provided herein, numerous specific details are set forth. It will be understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it is to be understood that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together into a single embodiment, figure, or its description. This disclosure, however, should not be interpreted as reflecting an intention that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will appreciate that the modules or units or components of the apparatus in the examples disclosed herein may be arranged in the apparatus as described in this embodiment, or alternatively may be positioned differently from the apparatus in this example in one or more devices. The modules in the preceding examples may be combined into one module or further divided into sub-modules.

Those skilled in the art will understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. The modules or units or components in the embodiments may be combined into one module or unit or component, and further they may be divided into multiple sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method so disclosed may be employed in any combination, unless at least some of such features and/or procedures or elements are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that although some of the embodiments described herein include certain features, but not others, included in other embodiments, that combinations of features of different embodiments are intended to be within the scope of the invention within and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

Furthermore, 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 means for performing the described functions. Thus, a processor having the necessary instructions for implementing the method or method element forms means for implementing the method or method element. Furthermore, an element of an apparatus embodiment described herein is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.

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

While the invention has been described in terms of a limited number of embodiments, those skilled in the art will appreciate, having the benefit of the above description, that other embodiments are conceivable within the scope of the invention thus described. Furthermore, it should be noted that the language used in this specification has been principally selected for readability and teaching purposes, rather than to explain or define the subject matter of the invention. Accordingly, many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the appended claims. This disclosure is intended to be illustrative and not restrictive with regard to the scope of the present invention, which is defined by the appended claims.

Claims (36)

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

sending the terminal equipment identification to a server;

receiving activation information returned by a server, wherein the activation information comprises an encrypted trusted identity, a trusted key and an activation code, the trusted identity and the trusted key correspond to the terminal equipment identifier, and the activation code is generated according to the terminal equipment identifier;

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

and encrypting and storing the trusted identity, the trusted key and the activation code into a secure storage space.

2. The method of claim 1, wherein the activation information comprises a ciphertext generated by encrypting the trusted identity, a trusted key, and an activation code ciphertext using a session key, the activation code ciphertext being a ciphertext generated by encrypting the activation code using the trusted key.

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

decrypting the activation information by adopting a session key to obtain a trusted identity, a trusted key and an activation code ciphertext;

and decrypting the activation code ciphertext by adopting the trusted key to obtain the activation code.

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

and verifying the activation code according to the terminal equipment identifier, and after the activation code passes verification, encrypting and storing the credible identity identifier, the credible secret key and the activation code into a safe storage space.

5. The method of claim 4, wherein the activation code includes usage right information of a trusted execution environment and verification information, the verification information including a ciphertext generated by encrypting the trusted identity, the usage right information, and a terminal device identity with the trusted key;

the step of verifying the activation code according to the terminal device identification comprises:

encrypting the trusted identity identification, the use authority information and the terminal equipment identification by adopting a trusted key to generate a first ciphertext;

and if the first ciphertext is consistent with the verification information, the activation code passes verification.

6. The method of claim 5, wherein the usage rights information includes validation time, expiration time, number of times available.

7. The method of claim 1, further comprising:

generating an authentication code according to the terminal equipment identifier;

and sending the authentication code to a server so that the server can verify the authentication code, and generating an activation code according to the terminal equipment identifier after the authentication code passes verification.

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

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

and decrypting the second ciphertext by adopting the preset key to obtain the session key and the terminal equipment identifier, calculating a second mapping value of the session key and the terminal equipment identifier by adopting the preset mapping function, and if the second mapping value is consistent with the first mapping value, passing the authentication code verification.

9. The method of claim 1, performed by an activation management application in the trusted execution environment, the secure storage space being accessible only 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 of activating a trusted execution environment, the trusted execution environment being deployed in a terminal device, the method comprising:

receiving a terminal equipment identifier sent by terminal equipment;

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

encrypting the trusted identity, a trusted key and an activation code to generate activation information;

sending the activation information to the terminal device so that the terminal device: and decrypting the activation information to obtain a trusted identity, a trusted key and an activation code, and encrypting and storing the trusted identity, the trusted key and the activation code to a secure storage space.

12. The method of claim 11, wherein the activation information is generated according to the steps of:

encrypting the activation code by using the trusted key to generate an activation code ciphertext;

and encrypting the trusted identity, the trusted key and the activation code ciphertext by adopting a session key to generate activation information.

13. The method of claim 11, wherein the activation code includes usage rights information of a trusted execution environment and verification information, the verification information including a ciphertext generated by encrypting the trusted identity, usage rights information, and terminal device identification with the trusted key.

14. The method of claim 13, wherein the usage rights information includes validation time, expiration time, number of times available.

15. The method of claim 11, further comprising:

receiving an authentication code sent by terminal equipment, wherein the authentication code is generated according to the terminal equipment identifier;

verifying the authentication code;

and after the authentication code passes verification, generating an activation code according to the terminal equipment identifier.

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

the step of verifying the authentication code comprises:

decrypting the first ciphertext by using the preset key to obtain the session key and the terminal equipment identifier;

calculating a second mapping value of the session key and the terminal equipment identifier by adopting the preset mapping function;

and if the second mapping value is consistent with the first mapping value, the authentication code passes the verification.

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

acquiring a trusted identity, a trusted key and an activation code of a trusted execution environment, wherein the activation code comprises use authority information and verification information of the trusted execution environment, and the verification information comprises a ciphertext generated by encrypting the trusted identity, the use authority information and a terminal equipment identifier by using the trusted key;

acquiring a terminal equipment identifier, and encrypting the trusted identity identifier, the use authority information and the terminal equipment identifier by adopting a trusted key to generate a first ciphertext;

and if the first ciphertext is consistent with the verification information and the current use environment of the terminal equipment is matched with the use authority information, the trusted execution environment is activated successfully.

18. A method for activating an application based on a trusted execution environment, the trusted execution environment being deployed in a terminal device, the method comprising:

sending the credible identity of the terminal equipment to a server:

receiving registration information returned by a server, wherein the registration information comprises a registration code encrypted by a trusted key corresponding to the trusted identity, and the registration code is generated according to the trusted identity;

decrypting the registration information by adopting a trusted key to obtain a registration code;

and encrypting and storing the registration code to a secure storage space.

19. The method as recited in claim 18, further comprising:

verifying whether the trusted execution environment is successfully activated;

and under the condition that the trusted execution environment is successfully activated, sending the trusted identity of the terminal equipment to the server.

20. The method of claim 18, wherein after the step of decrypting the registration information with a trusted key, further comprising:

and verifying the registration code according to the credible identity, and after the registration code passes verification, encrypting and storing the registration code to a safe storage space.

21. The method of claim 20, wherein the registration code includes usage rights information of the application to be activated and verification information, the verification information including a ciphertext generated by encrypting the trusted identity and the usage rights information with the trusted key;

the step of verifying the registration code in accordance with the trusted identity comprises:

encrypting the trusted identity and the use authority information by adopting a trusted key to generate a first ciphertext;

and if the first ciphertext is consistent with the verification information, the registration code passes verification.

22. The method of claim 21, wherein the usage rights information includes validation time, expiration time, number of times available.

23. The method as recited in claim 18, further comprising:

generating an authentication code according to the credible identity;

and sending the authentication code to a server so that the server can verify the authentication code, and generating a registration code according to the credible identity after the authentication code passes verification.

24. The method of claim 23, wherein the authentication code comprises a preset key, a second ciphertext and a first mapping value, the second ciphertext is a ciphertext generated by encrypting the trusted identity using the preset key, and the first mapping value is a value obtained by mapping the trusted identity using a preset mapping function;

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

and decrypting the second ciphertext by using the preset key to obtain the trusted identity, calculating a second mapping value of the trusted identity by using the preset mapping function, and if the second mapping value is consistent with the first mapping value, passing the authentication code verification.

25. The method of claim 18, performed by an activation management application in the trusted execution environment, the secure storage space being accessible only by the activation management application.

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

27. A method for activating an application based on a trusted execution environment, the trusted execution environment being deployed in a terminal device, the method comprising:

receiving a trusted identity sent by terminal equipment;

generating a registration code according to the credible identity;

encrypting the registration code by adopting a trusted key corresponding to the trusted identity to generate registration information;

sending the registration information to the terminal device so that the terminal device: decrypting the registration information by adopting a trusted key to obtain a registration code; and encrypting and storing the registration code to a secure storage space.

28. The method of claim 27, wherein the registration code includes usage rights information of the application to be activated and verification information, the verification information including a ciphertext generated by encrypting the trusted identity and the usage rights information with the trusted key.

29. The method of claim 28, wherein the usage rights information includes validation time, expiration time, number of times available.

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

31. The method of claim 27, further comprising:

receiving an authentication code sent by terminal equipment, wherein the authentication code is generated according to the credible identity;

verifying the authentication code;

and after the authentication code passes the verification, generating a registration code according to the credible identity.

32. The method of claim 31, wherein the authentication code includes a preset key, a first ciphertext and a first mapping value, the first ciphertext is a ciphertext generated by encrypting the trusted identity using the preset key, and the first mapping value is a value obtained by mapping the trusted identity using a preset mapping function;

the step of verifying the authentication code comprises:

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

calculating a second mapping value of the trusted identity by adopting the preset mapping function;

and if the second mapping value is consistent with the first mapping value, the authentication code passes the verification.

33. An application activation verification method based on a trusted execution environment, executed in the trusted execution environment of a terminal device, the method comprising:

acquiring a trusted identity, a trusted key and a registration code of an application to be verified, wherein the registration code comprises use authority information and verification information, and the verification information is a ciphertext generated by encrypting the trusted identity and the use authority information by using the trusted key;

encrypting the trusted identity and the use authority information by adopting the trusted key to generate a first ciphertext;

and if the first ciphertext is consistent with the verification information, the registration code is sent to an application to be verified, so that the application can determine whether the activation is successful according to the fact that whether the current use environment is matched with the use authority information.

34. A terminal device having a trusted execution environment deployed thereon,

the trusted execution environment comprises an activation management application adapted to perform the method of any one of claims 1-10, 17, 18-26, 33.

35. A server, comprising:

at least one processor; and

a memory storing program instructions configured for execution by the at least one processor, the program instructions comprising instructions for performing the method of any of claims 11-16, 27-32.

36. A trusted execution environment based application activation system, comprising:

the terminal device of claim 34; and

the server of claim 35.

Images