Secure Element Backup and Rollback Mechanism

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing secure elements lack a reliable mechanism for rolling back to a previous software version in case of update failures, leading to potential loss of functionality and requiring manual intervention for recovery.

Innovation Solution

A method and apparatus that includes an update agent handler and update agent for securely backing up the current software version, verifying updates, and performing a rollback if the update process fails, ensuring tamper-resistance and integrity of the backup and restore processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the secure element performs software updates using the standardized Open Firmware Loader mechanism, then the software can be updated securely with authentication and integrity checks, but if the update process fails, the secure element cannot boot the operating system anymore and requires manual intervention

Engineering Contradiction:

Improveupdate securityVSAvoidrecovery from update failure

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent creates a backup of the current working software version before performing the update. This preliminary action ensures that if the update fails, the secure element can restore the previous working version autonomously, eliminating the need for manual intervention and resolving the contradiction between secure updates and ease of recovery.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements a rollback mechanism that prepares a recovery path in advance by storing the backup version. This cushioning mechanism protects against update failures by providing a pre-prepared fallback option, allowing the secure element to recover automatically without requiring external intervention.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

2Productivity

If the secure element deletes the previously installed software version before updating, then the update process can proceed with the new version, but if the update fails, the secure element must wait for another update to regain functionality

Engineering Contradiction:

Improveupdate efficiencyVSAvoidfunctionality availability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

Instead of deleting the previous version before updating, the patent creates a backup of the current version first. This preliminary action preserves the ability to restore functionality if the update fails, resolving the contradiction between update efficiency and functionality availability.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements a mechanism where the previous software version is discarded (deleted) during the update process, but a backup is created and stored externally. If the update fails, the system can recover by retrieving and restoring the backed-up version, thus maintaining both update efficiency and reliability.

Inventive Principle:

Principle #34Discarding and recovering

3Reliability

If the secure element implements a rollback mechanism to restore previous software versions, then update failures can be recovered from automatically, but the secure element requires additional storage and processing capabilities

Engineering Contradiction:

Improveupdate failure recoveryVSAvoidbackup and restore mechanism

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the backup and restore functionality from the secure element's internal memory by storing the software backup externally on the device. This extraction reduces the complexity burden on the secure element while maintaining the reliability benefits of automatic rollback capability.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary mechanism where the device (not the secure element itself) stores and manages the software backup. This intermediary approach allows the secure element to implement rollback functionality without requiring extensive internal storage and processing capabilities, thus reducing device complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20240354091A1Update backup and failsafe rollback in secure elements

Publication Date: 2024.10.24 GIESECKE DEVRIENT MOBILE SECURITY GERMANY GMBH

AI summary

A method and an apparatus for updating software loaded on a secure element, SE, which SE comprises an update agent handler, and an update agent. In a first step, a request to backup a current version of software loaded on the SE is received at the SE. The request is sent from a device, external to the SE. Upon receiving the backup request, the SE performs a secure backup of the current software version, and returns the software backup to the device, to be stored thereon. In a further step, the SE performs an update process of the current software version, to obtain an updated software version. If the update process fails, a rollback is performed at the SE to restore the software backup as a new current soft-ware version on the SE.