Visible to Intel only — GUID: GUID-76729278-3BAA-4181-8FA6-C282612DBC78
Intel® AMT
Cryptography
Events
Trusted Application-to-Host Event Flow
Limitation
Inter-Applet Communication (IAC)
Monotonic Counters
OEM Signing
Platform Seed
Applet Attestation Using Intel® Enhanced Privacy ID (Intel® EPID)
SSL\\TLS
Secure Display
Secure Storage
Secure Time
Sessions
Applet Encryption
Timers
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-76729278-3BAA-4181-8FA6-C282612DBC78
Events
Intel® DAL supports sending and receiving events from other trusted applications or native services. To use events, trusted applications must define a special permission in the trusted application manifest to send/receive events. Trusted application events are sent to all instances of the same trusted application but not to a specific trusted application instance. In contrast, native events are sent to a specific instance of a trusted application.
The event mechanism can be utilized by Intel DAL services (e.g., timers), but to use them, event permissions have to be included when these services are implemented.
Trusted applications can also send events to host applications using the SendAnyMessage() method.
Note: Trusted applications cannot process commands from the host and process events simultaneously.
Note: Sending too many events will fill up the event queue, resulting in the loss of some of the messages.
Trusted Application-to-Host Event Flow
An application registers for events for a given non-shared session and passes a callback function using JHI_RegisterEvents. A thread is created at the application side by the JHI.dll and waits for events from the Intel DAL Host Interface Service. When a session posts an asynchronous event to the application, the event data is passed to the spooler. The spooler sends the event data to the Intel DAL Host Interface Service. The Intel DAL Host Interface Service notifies the application event thread that an event has arrived. The application event thread pulls the event data from the JHI service. The event thread invokes the application callback function with the event data as input. When the application calls JHI_UnRegisterEvents, the event thread is removed from the application. The flow begins and ends with the application.
Limitation
The virtual machine event queue is limited in size to 20 events. If, for some reason, the event queue is filled by unconsumed events (such as Timers, Capability Licensing Service & Applet), a new event will be dropped and never recovered.
Supported from API level 2