# US 2026/0099631 A1 · Method and apparatus for trust domain creation and destruction

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0099631 A1
- Document ID: US20260099631A1
- Status: Published application
- Kind: A1
- Application number: 19/342,443
- Filed: 2025-09-26
- Published: 2026-04-09
- Earliest claimed: 2018-12-20
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: Hormuzd Khosravi; Dror Caspi; Arie AHARON
- Web page: https://patentgrep.com/patent/US20260099631A1

## CPC

- G06F 21/72: in cryptographic circuits
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 9/5016: {the resource being the memory}
- G06F 21/575: {Secure boot}
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/79: in semiconductor storage media, e.g. directly-addressable memories
- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/0897: {involving additional devices, e.g. trusted platform module [TPM], smartcard or USB}
- G06F 2009/45583: {Memory management, e.g. access or allocation}
- G06F 2009/45587: {Isolation or security of virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method of creating a trusted execution domain includes initializing, by a processing device executing a trust domain resource manager (TDRM), a trust domain control structure (TDCS) and a trust domain protected memory (TDPM) associated with a trust domain (TD). The method further includes generating a one-time cryptographic key, assigning the one-time cryptographic key to an available host key id (HKID) in a multi-key total memory encryption (MK-TME) engine, and storing the HKID in the TDCS. The method further includes associating a logical processor to the TD, adding a memory page from an address space of the logical processor to the TDPM, and transferring execution control to the logical processor to execute the TD.

## Claims

### Claim at position 1

-20. (canceled)

### Claim 21

A non-transitory machine-readable storage medium, the machine-readable storage medium storing code that when executed by a machine is to cause the machine to perform operations corresponding to instructions from a resource manager to manage a secure software execution environment, including to:
perform operations corresponding to a first instruction having as a parameter a first address of a first page for a control structure for the secure software execution environment, including to initiate creation of the secure software execution environment, generate a first key, and assign the first key for use by the secure software execution environment;
perform operations corresponding to a second instruction to associate a second key to be used by the secure software execution environment with an available key identifier by programming the second key into a multi-key memory encryption circuit;
perform operations corresponding to a third instruction having as a parameter a second address, including to encrypt a second page and to add the encrypted second page to the secure software execution environment at the second address;
perform operations corresponding to a fourth instruction having as a parameter the second address of the encrypted second page, including to remove the encrypted second page from the secure software execution environment; and
perform operations corresponding to a fifth instruction to initiate destruction of the secure software execution environment.

### Claim 22 (depends on 21)

The machine-readable storage medium of claim 21, wherein writes by a software to the first page for the control structure are blocked in a memory ownership table to be used to assign the first page for the control structure to the secure software execution environment.

### Claim 23 (depends on 21)

The machine-readable storage medium of claim 21, wherein to perform the operations corresponding to the third instruction further include to consult a memory ownership table that is to be used to assign the encrypted second page to the secure software execution environment to determine whether to allow access to the encrypted second page.

### Claim 24 (depends on 21)

The machine-readable storage medium of claim 21, wherein the first page for the control structure for the secure software execution environment is not writable by a hypervisor and its contents cannot be read by the hypervisor.

### Claim 25 (depends on 21)

The machine-readable storage medium of claim 21, wherein to perform the operations corresponding to the third instruction to encrypt the second page includes to encrypt a state save page for the secure software execution environment.

### Claim 26 (depends on 21)

The machine-readable storage medium of claim 21, wherein to perform the operations corresponding to the fourth instruction to remove the encrypted second page includes to remove any one of multiple different types of the encrypted second page.

### Claim 27 (depends on 21)

The machine-readable storage medium of claim 21, wherein to perform the operations corresponding to the fourth instruction to remove the encrypted second page includes to remove an encrypted state save page for the secure software execution environment.

### Claim 28

An apparatus comprising:
a multi-key memory encryption circuit; and
a core to execute instructions for a resource manager to manage a secure software execution environment, the instructions comprising:
a first instruction having as a parameter a first address of a first page for a control structure for the secure software execution environment, the first instruction when executed to initiate creation of the secure software execution environment, generate a first key, and assign the first key for use by the secure software execution environment;
a second instruction that when executed is to associate a second key to be used by the secure software execution environment with an available key identifier by programming the second key into the multi-key memory encryption circuit;
a third instruction having as a parameter a second address, the third instruction when executed to encrypt a second page and to add the encrypted second page to the secure software execution environment at the second address;
a fourth instruction having as a parameter the second address of the encrypted second page, the fourth instruction when executed to remove the encrypted second page from the secure software execution environment; and
a fifth instruction that when executed is to initiate destruction of the secure software execution environment and to cause the secure software execution environment to stop executing.

### Claim 29 (depends on 28)

The apparatus of claim 28, wherein the first instruction when executed is to block writes by a software to the first page for the control structure in a memory ownership table that is to be used to assign the first page for the control structure to the secure software execution environment.

### Claim 30 (depends on 28)

The apparatus of claim 28, wherein the third instruction that when executed is to encrypt the second page is to encrypt a state save page for the secure software execution environment, wherein the third instruction when executed is to consult a memory ownership table that is to be used to assign the encrypted second page to the secure software execution environment to determine whether to allow access to the encrypted second page.

### Claim 31 (depends on 28)

The apparatus of claim 28, wherein the fourth instruction that when executed is to remove the encrypted second page is to remove any one of multiple different types of the encrypted second page, and wherein the first page for the control structure for the secure software execution environment is not writable by a hypervisor and its contents cannot be read by the hypervisor.

### Claim 32 (depends on 28)

The apparatus of claim 28, wherein the fourth instruction that when executed is to remove the encrypted second page is to remove an encrypted state save page for the secure software execution environment.

### Claim 33

A non-transitory machine-readable storage medium storing code that when executed by a machine is to cause the machine to perform operations corresponding to instructions from a resource manager to manage a secure software execution environment, including to:
perform operations corresponding to a first instruction having as a parameter a first address of a first page for a control structure for the secure software execution environment, including to initiate creation of the secure software execution environment and allocate the first page for use as the control structure;
perform operations corresponding to a second instruction having as a parameter a second address, including to add a second page to the secure software execution environment at the second address;
perform operations corresponding to a third instruction to extend a measurement for the secure software execution environment based on contents of a third page added to the secure software execution environment, wherein the measurement is based on a hash algorithm;
perform operations corresponding to a fourth instruction having as a parameter a third address, including to add a state save page to the secure software execution environment at the third address;
perform operations corresponding to a fifth instruction having as a parameter the third address, including to remove the state save page from the secure software execution environment; and
perform operations corresponding to a sixth instruction to destroy the secure software execution environment.

### Claim 34 (depends on 33)

The machine-readable storage medium of claim 33, wherein to perform the operations corresponding to the fourth instruction include to bind the state save page to a virtual processing space for the secure software execution environment.

### Claim 35 (depends on 33)

The machine-readable storage medium of claim 33, wherein to perform the operations corresponding to the third instruction include to store the extended measurement in the first page allocated for use as the control structure.

### Claim 36 (depends on 33)

The machine-readable storage medium of claim 33, wherein the first page allocated for use as the control structure is not readable by the resource manager.

### Claim 37 (depends on 33)

The machine-readable storage medium of claim 33, perform operations corresponding to at least one instruction to access a memory ownership table, the memory ownership table to indicate that the second page is accessible by the secure software execution environment but not by the resource manager.

### Claim 38

An apparatus comprising:
a memory controller to provide access to a memory; and
a core to execute instructions for a resource manager to manage a secure software execution environment, the instructions comprising:
a first instruction having as a parameter a first address of a first page for a control structure for the secure software execution environment, the first instruction when executed to initiate creation of the secure software execution environment and allocate the first page for use as the control structure;
a second instruction having as a parameter a second address, the second instruction when executed to add a second page to the secure software execution environment at the second address;
a third instruction that when executed is to extend a measurement for the secure software execution environment based on contents of a third page added to the secure software execution environment, wherein the measurement is based on a hash algorithm;
a fourth instruction having as a parameter a third address, the fourth instruction when executed to add a state save page to the secure software execution environment at the third address;
a fifth instruction having as a parameter the third address, the fifth instruction when executed to remove the state save page from the secure software execution environment; and
a sixth instruction that when executed is to destroy the secure software execution environment.

### Claim 39 (depends on 38)

The apparatus of claim 38, wherein the fourth instruction when executed is to bind the state save page to a virtual processing space for the secure software execution environment.

### Claim 40 (depends on 38)

The apparatus of claim 38, wherein the third instruction when executed is to store the extended measurement in the first page allocated for use as the control structure.

### Claim 41 (depends on 38)

The apparatus of claim 38, wherein the first page allocated for use as the control structure is not readable by the resource manager.

### Claim 42 (depends on 38)

The apparatus of claim 38, at least one instruction that when executed is to access a memory ownership table, the memory ownership table to indicate that the second page is accessible by the secure software execution environment but not by the resource manager.

### Claim 43

A non-transitory machine-readable storage medium storing code that when executed by a machine is to cause the machine to perform operations corresponding to instructions from a resource manager to manage a secure software execution environment, including to:
perform operations corresponding to a first instruction having as a parameter a first address of a first page for a control structure for the secure software execution environment, including to initiate creation of the secure software execution environment and allocate the first page for use as the control structure;
perform operations corresponding to a second instruction to configure a cryptographic key for the secure software execution environment on at least one package on which the secure software execution environment is to be executed;
perform operations corresponding to a third instruction having as a parameter a second address, including to add a state save page to the secure software execution environment at the second address;
perform operations corresponding to a fourth instruction having as a parameter a third address, including to add a second page to the secure software execution environment at the third address, wherein contents of the second page are to be encrypted with the cryptographic key; and
perform operations corresponding to a fifth instruction having as a parameter the third address of the second page, including to remove the second page from the secure software execution environment, wherein the fifth instruction allows the second page to be any one of a plurality of different types, including a type for a control structure and a type for an extended page table.

### Claim 44 (depends on 43)

The machine-readable storage medium of claim 43, further storing code that when executed by the machine is to cause the machine to perform operations corresponding to a sixth instruction from the resource manager, including to initiate destruction of the secure software execution environment.

### Claim 45 (depends on 43)

The machine-readable storage medium of claim 43, wherein to perform the operations corresponding to the third instruction include to bind the state save page to a trust domain virtual processing space page of the secure software execution environment.

### Claim 46 (depends on 43)

The machine-readable storage medium of claim 43, wherein to perform the operations corresponding to the first instruction include to indicate the cryptographic key to be used by the secure software execution environment.

### Claim 47 (depends on 43)

The machine-readable storage medium of claim 43, wherein the secure software execution environment is a trust domain.
