Visible to Intel only — GUID: GUID-D147E343-1795-47A0-882A-4C398D0400B0
For API Level 1 - Intel® ME 7.x - Sandy Bridge
For API Level 1.1 - Intel® ME 8.x lite - Sandy Bridge
For API Level 2 - Intel® ME 8.0 - Ivy Bridge
For API Level 3 - Intel® ME 8.1 - Ivy Bridge
For API Level 3 - SEC1.0, SEC1.1, SEC1.2, SEC2.0
For API Level 4 - Intel® ME 9.5, Intel ME 9.5.55 - Haswell
For API Level 4 - Intel® ME 9.1, Intel ME 9.1.35 - Haswell
For API Level 5 - Intel® ME 10.0.0 - Haswell
For API Level 6 - Intel® ME 10.0.20 - Broadwell
For API Level 7 - ME 11.0 - Skylake_LP and Skylake_H
For API Level 8 - TXE3.0 - Broxton, ME 11.5/11.8 - Kabylake_LP, Kabylake_H
For API Level 9 - Intel® ME 12.0 - Cannon Lake
Trusted Application Validation Guidelines
Validating the Manifest
Memory and Performance
Error Handling and Recovery
Functional Validation and Multi-Instance Support
Pack and DALP Generation and Validation
Host-Side Software Validation Guidelines
Trusted Application Management Flows
Error Handling and Recovery Flows
Multi-Instance and Interoperability Testing of Trusted Application Management
General and Platform-Related Events
End-to-End and Setup Validation Guidelines
Cross Trusted Application Interoperability Functional Testing
Creating a New Project
Importing an Existing Project
Converting an Existing Project
Building and Packaging Your Project and Running in Emulated Environment
Running Your Project
Running and Testing on Emulation and on Silicon
Debugging Trusted Applications
Preparing and Submitting Your Project for Signing
Signing an Applet
Signing New Versions
Visible to Intel only — GUID: GUID-D147E343-1795-47A0-882A-4C398D0400B0
Inter-Applet Communication (IAC)
The Intel® DAL Inter-Applet Communication (IAC) feature allows a service trusted application (TA) to provide certain platform services (e.g., Secure Display) to other client TAs via internal sessions.
This IAC feature has the following attributes:
- Reliable and synchronous communication. The client TA will wait for the IAC result and then continue.
- The service TA supports multiple internal sessions from multiple client applets.
- The service TA knows the client TA's UUID and can decide how to continue its flow accordingly.
- The service TA must run before client TAs attempt to to open internal sessions to it. If an internal session is opened while the service TA is not running, the system returns an error.
- Internal sessions must be closed before trying to stop the service TA from running; first close the session between the client and the service TA.
- The service TA should specify in the manifest the number of sessions that can be opened to it.
- Each client TA should specify in the manifest the UUIDs of the service applets to which it can open sessions.
See the IAC sample for more details.
Supported from API level 7