Distributed Secure Controller Task Routine Compilation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing secure processing systems face challenges in efficiently distributing and executing task routines across multiple secure controllers with different processor components, as they often have distinct instruction sets and resources, leading to difficulties in compiling and executing security tasks like authentication and encryption in a unified manner.

Innovation Solution

The system compiles task routines into multiple versions tailored for different processor components and distributes them among secure controllers, allowing for dynamic selection based on available resources and instruction sets, enabling distributed execution of security functions such as authentication and encryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If task routines are compiled into multiple versions for different processor components and distributed among secure controllers, then the adaptability and resource utilization of the secure processing system are improved, but the device complexity and difficulty of managing distributed execution increase

Engineering Contradiction:
ImproveadaptabilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The task routine is segmented into multiple versions, each tailored for specific processor components (e.g., x86, ARM, RISC-V). Each secure controller receives and executes only the version compatible with its processor architecture, enabling adaptability without requiring each controller to handle all possible instruction sets.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The secure processing system is designed to support multiple processor architectures universally. By compiling task routines into multiple versions and distributing them appropriately, the system achieves multi-functionality across diverse hardware platforms while maintaining a unified security management approach.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If secure controllers are isolated from the operating system and applications software to prevent tampering, then the security and integrity of task routines are improved, but the ease of operation and system integration deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

A trusted execution environment acts as an intermediary between the isolated secure controllers and the untrusted main processing environment. This mediator enables secure controllers to execute task routines with high security while still allowing controlled interaction with the operating system and applications through defined interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The computing system is segmented into distinct trusted and untrusted environments. Secure controllers operate in the isolated trusted environment for critical security functions, while the main processor handles general operations. This segmentation maintains security boundaries while enabling necessary system integration through controlled communication channels.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If multiple secure controllers with different instruction sets are used to handle various processor components, then the versatility and coverage of the secure processing system are improved, but the difficulty of compiling and distributing task routines increases

Engineering Contradiction:
ImproveversatilityVSAvoidcompilation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Task routines are pre-compiled into multiple version variants corresponding to different processor instruction sets before distribution. This preliminary compilation action eliminates the need for runtime compilation or interpretation, simplifying the execution process on diverse hardware while maintaining versatility across different secure controllers.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The compilation process generates different versions of task routines with varying parameters optimized for specific instruction sets (x86, ARM, RISC-V). By changing compilation parameters to target different architectures, the system achieves versatility without requiring complex runtime adaptation logic at each secure controller.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11656853B2Techniques for distributed operation of secure controllers
Publication Date: 2023.05.23 INTEL CORP
  • US11656853B2 patent drawing
  • US11656853B2 patent drawing
  • US11656853B2 patent drawing

AI summary

Various embodiments are generally directed to techniques for supporting the distributed execution of a task routine among multiple secure controllers incorporated into multiple computing devices. An apparatus includes a first processor component and first secure controller of a first computing device, where the first secure controller includes: a selection component to select the first secure controller or a second secure controller of a second computing device to compile a task routine based on a comparison of required resources to compile the task routine and available resources of the first secure controller; and a compiling component to compile the task routine into a first version of compiled routine for execution within the first secure controller by the first processor component and a second version for execution within the second secure controller by a second processor component in response to selection of the first secure controller. Other embodiments are described and claimed.