Data processing method and terminal

Abstract

A data processing method includes determining whether a first conflicting application related to a first conflicting peripheral is in a whitelist, independently taking over the first conflicting peripheral in response to the first conflicting application being in the whitelist, where the first conflicting application runs in a rich execution environment (REE), and sending data generated by the first conflicting peripheral to the first conflicting application in response to a trusted user interface (TUI) being displayed.

What is claimed is: 
     
       1. A terminal, comprising:
 at least one processor; and 
 a memory coupled to the at least one processor and configured to store programming instructions that, when executed by the at least one processor, cause the terminal to:
 determine whether a first conflicting application related to a first conflicting peripheral is in a whitelist; 
 send an application permission verification complete message to a rich execution environment (REE) management circuit, wherein the application permission verification complete message instructs the REE management circuit to release control permission for the first conflicting peripheral; 
 independently take over the first conflicting peripheral in response to the first conflicting application being in the whitelist, wherein the first conflicting application runs in an REE; 
 establish a data channel for communicating with the first conflicting application, wherein the data channel transmits data of a target data type, and wherein the target data type is a type of data transmitted between the first conflicting application and the first conflicting peripheral and defined in the whitelist; and 
 send data generated by the first conflicting peripheral to the first conflicting application in response to a trusted user interface (TUI) being displayed. 
 
 
     
     
       2. The terminal of  claim 1 , wherein the programming instructions that, when executed by the at least one processor, cause the terminal to determine whether the first conflicting application related to the first conflicting peripheral is in the whitelist comprises the terminal being caused to:
 receive an application permission request message from an REE management circuit, wherein the application permission request message carries an identifier of the first conflicting application and an identifier of the first conflicting peripheral; and 
 determine, based on the identifier of the first conflicting application and the identifier of the first conflicting peripheral, whether the first conflicting application and the first conflicting peripheral are in the whitelist. 
 
     
     
       3. The terminal of  claim 1 , wherein a data type of the data generated by the first conflicting peripheral is the target data type, and wherein the programming instructions that, when executed by the at least one processor, cause the terminal to send the data generated by the first conflicting peripheral to the first conflicting application comprises the terminal being configured to send the data generated by the first conflicting peripheral to the first conflicting application. 
     
     
       4. The terminal of  claim 3 , wherein when executed by the at least one processor, the programming instructions further cause the terminal to send a notification message to the REE management circuit notifying that a display of the TUI terminates and that the REE management circuit is to take over the first conflicting peripheral again. 
     
     
       5. The terminal of  claim 1 , wherein the whitelist comprises an application list. 
     
     
       6. The terminal of  claim 1 , wherein the whitelist comprises an application identifier and a peripheral identifier. 
     
     
       7. The terminal of  claim 1 , wherein the whitelist comprises an application identifier and a data type. 
     
     
       8. The terminal of  claim 1 , wherein the REE comprises an ANDROID operating system. 
     
     
       9. The terminal of  claim 1 , wherein the REE comprises an iOS operating system. 
     
     
       10. The terminal of  claim 1 , wherein the TUI is controlled by a trusted application that invokes the TUI. 
     
     
       11. A terminal, comprising:
 at least one processor; and 
 a memory coupled to the at least one processor and configured to store programming instructions that, when executed by the at least one processor, cause the terminal to:
 determine a first conflicting peripheral that conflicts with a trusted user interface (TUI); 
 determine a first conflicting application related to the first conflicting peripheral; 
 receive a permission verification complete message from a trusted execution environment (TEE) management circuit, wherein the permission verification complete message indicates that the first conflicting application is in a whitelist of a TEE; 
 release control permission for the first conflicting peripheral according to the permission verification complete message; 
 establish a data channel for communicating with the TEE management circuit, wherein the data channel transmits data of a target data type, and wherein the target data type is a type of data transmitted between the first conflicting application and the first conflicting peripheral and defined in the whitelist; 
 allow, based on the permission verification complete message, the first conflicting application to receive data generated by the first conflicting peripheral, wherein the first conflicting application runs in a rich execution environment (REE); and 
 allow the first conflicting application to receive the data generated by the first conflicting peripheral from the TEE management circuit in response to the TUI being displayed. 
 
 
     
     
       12. The terminal of  claim 11 , wherein when executed by the at least one processor, the programming instructions further cause the terminal to send an application permission request message to the TEE management circuit, and wherein the application permission request message carries an identifier of the first conflicting application and an identifier of the first conflicting peripheral to enable the TEE management circuit to determine whether the first conflicting application and the first conflicting peripheral are in the whitelist. 
     
     
       13. The terminal of  claim 11 , wherein the programming instructions that, when executed by the at least one processor, cause the terminal to allow the first conflicting application to receive the data generated by the first conflicting peripheral from the TEE management circuit comprises the terminal being configured to allow the first conflicting application to receive, using the data channel, data of the target data type generated by the first peripheral conflicting peripheral. 
     
     
       14. The terminal of  claim 13 , wherein when executed by the at least one processor, the programming instructions further cause the terminal to receive a notification message from the TEE management circuit, and wherein the notification message notifies that a display of the TUI terminates and that an REE management circuit is to take over the first conflicting peripheral again. 
     
     
       15. A data processing method, comprising:
 determining whether a first conflicting application related to a first conflicting peripheral is in a whitelist; 
 sending an application permission verification complete message to a rich execution environment (REE) management circuit, wherein the application permission verification complete message instructs the REE management circuit to release control permission for the first conflicting peripheral; 
 independently taking over the first conflicting peripheral in response to the first conflicting application being in the whitelist, wherein the first conflicting application runs in an REE; 
 establishing a data channel for communicating with the first conflicting application, wherein the data channel transmits data of a target data type, and wherein the target data type is a type of data transmitted between the first conflicting application and the first conflicting peripheral and defined in the whitelist; and 
 sending data generated by the first conflicting peripheral to the first conflicting application in response to a trusted user interface (TUI) being displayed. 
 
     
     
       16. The data processing method of  claim 15 , wherein determining whether the first conflicting application is in the whitelist comprises:
 receiving an application permission request message from the REE management circuit, wherein the application permission request message carries an identifier of the first conflicting application and an identifier of the first conflicting peripheral; and 
 determining, based on the identifier of the first conflicting application and the identifier of the first conflicting peripheral, whether the first conflicting application and the first conflicting peripheral are in the whitelist. 
 
     
     
       17. The data processing method of  claim 15 , wherein a data type of the data generated by the first conflicting peripheral is the target data type, and wherein sending the data generated by the first conflicting peripheral to the first conflicting application comprises sending the data generated by the first conflicting peripheral to the first conflicting application. 
     
     
       18. The data processing method of  claim 17 , further comprising sending a notification message to the REE management circuit, wherein the notification message notifies the REE management circuit that a display of the TUI terminates and that the REE management circuit is to take over the first conflicting peripheral again.