Mobile Platform Secure Update via Trusted Execution Environment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices lack secure user authentication mechanisms for operating system and firmware updates, allowing unauthorized users to bypass security and potentially roll back changes, and there is no verification mechanism to ensure that updates include all necessary software components.

Innovation Solution

Implementing a trusted execution environment (TEE) with a secure update application module and database to verify the inclusion of critical software components and authenticate users before allowing updates, ensuring secure and authorized software installations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If automatic wireless software updates are implemented with reduced user involvement, then user convenience and experience are improved, but secure user authentication is compromised allowing unauthorized updates

Engineering Contradiction:
Improveuser convenienceVSAvoidsecure authentication
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments the update verification process into multiple independent components: digital signature verification, hash validation, component presence verification, and rollback prevention checks. Each segment performs a specific security function, allowing automated updates to maintain convenience while ensuring comprehensive authentication through divided security checks

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary security actions before allowing updates: verifying digital signatures of update packages, checking hash values to ensure integrity, confirming presence of required software components, and preventing rollback to previous versions. These preliminary verifications are automatically executed before update installation, maintaining both convenience and security

Inventive Principle:
Principle #10Preliminary action

2Reliability

If update verification mechanisms are added to ensure software component integrity, then security and reliability are improved, but system complexity increases

Engineering Contradiction:
Improveupdate verificationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The update system performs self-verification through automated digital signature validation, hash checking, and component presence verification. The system independently validates update integrity and security requirements without requiring external manual verification, maintaining reliability while managing complexity through automation

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms where each verification step (signature validation, hash check, component verification) provides pass/fail feedback that determines whether the update proceeds. This structured feedback approach ensures comprehensive verification while managing complexity through clear decision points at each verification stage

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9953165B2Mobile platform software update with secure authentication
Publication Date: 2018.04.24 TAHOE RES LTD
  • US9953165B2 patent drawing
  • US9953165B2 patent drawing
  • US9953165B2 patent drawing

AI summary

Generally, this disclosure describes devices, methods and systems and for securely updating software on a mobile platform using trusted hardware based authentication. The device may include an image update module configured to receive a software update image from an update server, the image update module executing at an operating system (OS) level; a critical component database configured to identify critical software components associated with the secure operation of the device; a secure update application module configured to verify the inclusion of the critical software components in the software update image prior to installation of the software update image on the device; and a trusted execution environment (TEE) configured to restrict control access and data access to the secure update application module and the critical component database, the restriction enforced against the OS and against modules executing at the OS level.