While the TEE Internal Core API offers the possibility to execute all sensitive operations within a Trusted Application (TA) running in the Trusted Execution Environment (TEE), certain applications need to expose sensitive information to the user for validation or need to get sensitive information from the user. Entering a PIN and signing a document are examples of operations that need to be handled inside the TEE for the Trusted Application and not to rely on facilities in the Rich Execution Environment (REE).
As had been previously road mapped, this version of the specification passes ownership of the specification of the generic events and peripheral system over to the TEE Internal Core API v1.2, and will be published alongside or slightly after TEE Internal Core API 1.2
Previous Version(s)
While the TEE Internal Core API offers the possibility to execute all sensitive operations within a Trusted Application (TA) running in the Trusted Execution Environment (TEE), certain applications need to expose sensitive information to the user for validation or need to get sensitive information from the user. Entering a PIN and signing a document are examples of operations that need to be handled inside the TEE for the Trusted Application and not to rely on facilities in the Rich Execution Environment (REE).
This specification defines a low-level interface to a frame buffer and input events, which the Trusted Application can use to create custom user interfaces. The event loop can also be used to retrieve events from other peripherals not related to TUI. Because of this, the event loop will be moved to TEE Internal Core API in v1.2.
