Secure Software Installation via Region Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for installing secure software in devices with partitioned non-volatile memory are cumbersome, requiring special tools and increasing development costs, as they necessitate the OEM to handle all secure software installations, which is impractical for manufacturers dealing with diverse batches and constrained resources.

Innovation Solution

A method where target software is initially installed in a less secure region and verified using standard tools, then the region is updated to a more secure status, allowing non-secure installation tools to be used without the need for dedicated secure-installation tooling, thereby simplifying the process and reducing costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If secure software is installed directly in a more secure region using standard tools, then security is compromised, but if installed in a less secure region first, then installation becomes simpler

Engineering Contradiction:
Improveinstallation processVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies preliminary action by first installing the secure software image in a less secure region using standard installation tools, then subsequently migrating it to the secure region after verification. This preliminary installation step simplifies the overall process while maintaining security through the two-stage approach.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The less secure region acts as an intermediary medium during the installation process. Standard installation tools install the software image in this intermediate location, which then serves as a temporary holding area before the final migration to the secure region, enabling the use of conventional tools without compromising security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If OEM handles all secure software installations, then security is maintained, but device complexity and development costs increase

Engineering Contradiction:
ImprovesecurityVSAvoidinstallation process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables self-service installation by allowing standard installation tools to install secure software images in the less secure region autonomously. The access control circuitry automatically verifies the software and performs the migration to the secure region, eliminating the need for OEM-specific manual installation processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent makes the installation process universal by enabling standard installation tools to handle secure software installation through the two-stage process. This multi-functional approach allows the same tools to install both secure and non-secure software, eliminating the need for specialized OEM installation procedures.

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

3Reliability

If verification is performed before region update, then security is ensured, but installation time increases

Engineering Contradiction:
Improvesoftware verificationVSAvoidinstallation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Verification is performed as a preliminary action before the region update occurs. The access control circuitry verifies the software image in the less secure region before migrating it to the secure region, ensuring security is maintained while the process remains efficient through automated verification.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11429364B2Software installation method
Publication Date: 2022.08.30 QUALCOMM TECHNOLOGIES INC
  • US11429364B2 patent drawing
  • US11429364B2 patent drawing
  • US11429364B2 patent drawing

AI summary

A software installation method is provided for a device comprising non-volatile memory 10 and access control circuitry 6 to control access to the non-volatile memory based on region defining data 7 defining whether a given region of the non-volatile memory is a less secure region or a more secure region, with greater access restriction imposed on access to a more secure region than to a less secure region. The method comprises installing target software 40 in a target region of the non-volatile memory 10 defined by the region defining data as a less secure region; verifying the target software; and at least when verification of the target software is successful, and after installation of the target software, updating the region defining data 7 to change the target region from a less secure region to a more secure region.