Trusted Execution Environment for IoT OS Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Low-cost IoT devices face challenges in authenticating with wireless communication networks without creating processing burdens on roaming networks and mitigating fraudulent access, as existing methods are inefficient and prone to OS alteration.
Innovation Solution
Pre-loading multiple approved operating systems in IoT devices during manufacturing, with a trusted execution environment validating the OS integrity by calculating checksums and rebooting to the appropriate OS upon network switch, thereby authenticating securely and efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If existing authentication methods are used in low-cost IoT devices, then device cost is reduced, but processing burden on roaming networks increases and fraudulent access risk increases
Solution Approach 1:
The patent pre-loads multiple approved operating systems into the IoT device during manufacturing, each signed with unique cryptographic credentials. This preliminary preparation eliminates the need for complex runtime authentication processing on roaming networks, as the device can immediately present valid credentials upon detecting a network switch. The trusted execution environment validates the OS integrity beforehand, ensuring security without burdening the roaming network.
Solution Approach 2:
The patent introduces a trusted execution environment (TEE) as an intermediary between the untrusted rich execution environment (REE) and the authentication process. The TEE securely stores cryptographic credentials and validates OS integrity, acting as a mediator that prevents fraudulent access while maintaining device cost-effectiveness. This intermediary layer isolates security-critical operations from the potentially compromised REE, solving the contradiction between low cost and high security.
2Reliability
If multiple operating systems are pre-loaded in IoT devices, then authentication speed and reliability improve, but device memory requirements and complexity increase
Solution Approach 1:
The patent segments the device into two distinct execution environments: a trusted execution environment (TEE) for security-critical operations and an untrusted rich execution environment (REE) for general applications. Multiple operating systems are stored in a partitioned file system, with each OS associated with specific network operators. This segmentation allows the device to manage multiple OSes without proportionally increasing overall complexity, as the TEE provides a standardized security framework that simplifies the management of diverse OS components.
Solution Approach 2:
The trusted execution environment serves multiple functions: storing cryptographic credentials, validating OS integrity through checksum verification, managing the file system, and controlling the reboot process. This multi-functionality reduces the need for separate security modules for each function, thereby limiting the increase in device complexity while maintaining high authentication reliability across multiple operating systems.
3Reliability
If OS integrity validation is performed using checksum verification, then fraudulent access is prevented, but processing time and computational overhead increase
Solution Approach 1:
The patent performs OS integrity validation as a preliminary action during device initialization and network switching, rather than during authentication. The trusted execution environment calculates checksums of OS images and compares them against stored reference values before the device attempts to use the OS. This preliminary validation ensures that only intact OSes are activated, preventing fraudulent access while minimizing time loss during critical authentication moments.
Solution Approach 2:
The patent replaces complex cryptographic verification mechanisms with simpler checksum-based validation for OS integrity checking. While checksums provide less security than full cryptographic verification, they offer a practical balance for IoT devices, reducing computational overhead and validation time while still effectively detecting OS tampering. The TEE's secure storage of reference checksums ensures that this simplified mechanism maintains adequate reliability.
Data Source
AI summary
A method of attaching to a wireless communication network to receive wireless communication service. The method comprises calculating a checksum by a monitor application over at least a portion of an operating system stored in a wireless communication device, wherein the monitor application is stored in a trusted portion of memory of the device and executes in a trusted execution environment (TEE) of the device and wherein the operating system is authorized by a wireless communication network, comparing the calculated checksum value by the monitor application to a checksum value stored in the TEE, based on determining that the calculated checksum value matches the stored checksum value, rebooting the device to execute the operating system, and transmitting radio access credentials to the wireless communication network by the device, whereby the device authenticates into the wireless coverage of the wireless communication network based on the radio access credentials.