eUICC Installation State Machine for Secure OTA Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for updating and configuring secure elements in user devices, such as eUICCs, do not ensure future-proof functional safety and security while maintaining deployability and availability, often leading to compromised functionality and security due to inconsistent OS and secure element versions.
Innovation Solution
A method involving an installation state machine and operating system dataset that allows secure elements to be configured with an installation program dataset, enabling secure updates without altering user data, and ensuring compatibility and integrity through predefined and post-issuance conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If firmware updates are performed on secure elements, then functional safety and security are improved, but device complexity and update management difficulty increase
Solution Approach 1:
The patent applies preliminary action by defining a state machine with predefined states (INITIALIZED, SECURED, INSTALLED, LOCKED) and transition conditions before updates are performed. This pre-established framework enables automated update management, reducing complexity while ensuring functional safety and security through structured update processes.
Solution Approach 2:
The patent uses parameter changes by transitioning the secure element through different states (from INITIALIZED to SECURED to INSTALLED to LOCKED) based on update progress and security conditions. These state parameter changes provide a systematic way to manage update complexity while maintaining reliability.
2Ease of operation
If secure elements are updated over-the-air, then deployability and availability are improved, but risk of unauthorized data changes increases
Solution Approach 1:
The patent introduces an intermediary update agent that mediates between the external update source and the secure element. This agent verifies update packages, manages installation states, and ensures authorized changes only, enabling secure over-the-air updates while maintaining deployability and protecting against unauthorized modifications.
Solution Approach 2:
The state machine provides feedback mechanisms by monitoring transition conditions and update progress. This feedback ensures that only authorized updates can transition the system from SECURED to INSTALLED state, preventing unauthorized data changes while enabling convenient over-the-air deployment.
3Adaptability or versatility
If operating system versions are updated independently from secure element versions, then adaptability is improved, but functional safety and security are compromised
Solution Approach 1:
The patent merges OS version management with secure element version management through the unified state machine. The state transitions ensure that OS updates and secure element updates are coordinated, maintaining version compatibility and functional safety while still allowing adaptability through controlled update processes.
Solution Approach 2:
The state machine serves multiple functions: it manages secure element updates, coordinates OS version compatibility, verifies update packages, and controls system state transitions. This universal mechanism enables adaptability across different version scenarios while ensuring functional safety and security.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
A method, as well as a corresponding configuration program (10), an operating system dataset (O), a computer-readable data carrier (11, 12, 13), a user device (3), and a server device (4) are provided, wherein for configuring the user device (5), the steps of the method comprising the steps of providing a secure element (6) of the user device (5), such as an eUICC, with an installation program dataset (I) for managing at least parts of an installation process for loading data onto the secure element (6); wherein the installation program dataset (I) implements an installation state machine (20) located in the installation program dataset (I) and configured to provide information regarding a status of the installation process.