# US 2026/0099583 A1 · Implementation of device seamless update with pre-authorization policy in trusted execution environment

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

- Number: US 2026/0099583 A1
- Document ID: US20260099583A1
- Status: Published application
- Kind: A1
- Application number: 18/993,879
- Filed: 2022-08-25
- Published: 2026-04-09
- Earliest claimed: 2022-08-25
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: Jiewen Yao; Shamanna Datta; Mahesh Natu; Xiaoyu Ruan; Andrew Draper; Raghunandan Makaram; Alberto Munoz
- Web page: https://patentgrep.com/patent/US20260099583A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/575: {Secure boot}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04W 12/08: Access security
- 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)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A system and method of enhancing the implementation of device seamless updates with a pre-authorization policy in Trusted Execution Environments include setting a device update pre-authorization policy while establishing a connection with the device, indicating that pre-authorization is necessitated for updating the device, receiving a pre-authorization event from the device, where the pre-authorization event indicates an update for the device has been activated, determining whether the device is authorized to perform the update, and sending a response indicating whether the device is authorized to perform the update to the device.

## Claims

### Claim at position 1

-20. (canceled)

### Claim 21

A method comprising:
establishing, by a computing device, a pre-authorization policy regarding one or more remote computing devices while establishing a connection with a remote computing device of the one or more remote computing devices;
receiving a pre-authorization event from the remote computing device, wherein the pre-authorization event indicates an update for the remote computing device has been activated;
determining whether the remote computing device is authorized to perform the update; and
sending a response authorizing the remote computing device to perform the update at the remote computing device.

### Claim 22 (depends on 21)

The method of claim 21, wherein the update is authorized and performed in accordance with the pre-authorization policy, wherein the remote computing device is pre-authorized for update using a trusted execute environment (TEE) associated with the computing device, wherein the update is performed at the remote computing device using a virtual machine manager (VMM) associated with the remote computing device.

### Claim 23 (depends on 21)

The method of claim 21, wherein in response to receiving the pre-authorization event from the device, determining whether the device is authorized to perform the update comprises:
sending a request to the device for update information;
receiving the update information from the device; and
evaluating the update information to determine whether the remote computing device is ready to perform the update in accordance with the pre-authorization policy.

### Claim 24 (depends on 21)

The method of claim 21, wherein the computing device comprises processing circuitry coupled with a memory, the processing circuitry comprising one or more of application processing circuitry or graphics processing circuitry.

### Claim 25

A computing device comprising:
processing circuitry coupled to a memory, the processing circuitry to:
establish a pre-authorization policy regarding one or more remote computing devices while establishing a connection with a remote computing device of the one or more remote computing devices;
receive a pre-authorization event from the remote computing device, wherein the pre-authorization event indicates an update for the remote computing device has been activated;
determine whether the remote computing device is authorized to perform the update; and
send a response authorizing the remote computing device to perform the update at the remote computing device.

### Claim 26 (depends on 25)

The computing device of claim 25, wherein the update is authorized and performed in accordance with the pre-authorization policy, wherein the remote computing device is pre-authorized for update using a trusted execute environment (TEE) associated with the computing device, wherein the update is performed at the remote computing device using a virtual machine manager (VMM) associated with the remote computing device.

### Claim 27 (depends on 25)

The computing device of claim 25, wherein in response to receiving the pre-authorization event from the device and determining whether the device is authorized to perform the update, the processing circuitry is further to:
send a request to the device for update information;
receive the update information from the device; and
evaluate the update information to determine whether the remote computing device is ready to perform the update in accordance with the pre-authorization policy.

### Claim 28 (depends on 25)

The computing device of claim 25, wherein the processing circuitry comprises one or more of application processing circuitry or graphics processing circuitry.

### Claim 29

At least one computer-readable medium having stored thereon instructions which, when executed, cause a computing device to perform operations comprising:
establishing a pre-authorization policy regarding one or more remote computing devices while establishing a connection with a remote computing device of the one or more remote computing devices;
receiving a pre-authorization event from the remote computing device, wherein the pre-authorization event indicates an update for the remote computing device has been activated;
determining whether the remote computing device is authorized to perform the update; and
sending a response authorizing the remote computing device to perform the update at the remote computing device.

### Claim 30 (depends on 29)

The computer-readable medium of claim 29, wherein the update is authorized and performed in accordance with the pre-authorization policy, wherein the remote computing device is pre-authorized for update using a trusted execute environment (TEE) associated with the computing device, wherein the update is performed at the remote computing device using a virtual machine manager (VMM) associated with the remote computing device.

### Claim 31 (depends on 29)

The computer-readable medium of claim 29, wherein in response to receiving the pre-authorization event from the device, determining whether the device is authorized to perform the update comprises:
sending a request to the device for update information;
receiving the update information from the device; and
evaluating the update information to determine whether the remote computing device is ready to perform the update in accordance with the pre-authorization policy.

### Claim 32 (depends on 29)

The computer-readable medium of claim 29, wherein the computing device comprises one or more processors coupled to a memory, the one or more processors having one or more application processors or one or more graphics processors.
