Data Processing Method and Terminal

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;
• 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 a rich execution environment (REE);
• and
• send data generated by the first conflicting peripheral to the first conflicting application in response to a trusted user interface (TUI) being displayed.

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);
• determining 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;
• 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.

A data processing method, comprising:

• 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, wherein 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.