eUICC OS Update Compatibility Checks for Secure Data Formats
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for updating secure elements in user devices, such as eUICCs, do not ensure that the operating system and secure elements have the same origin and version, leading to potential compromises in functional safety, security, and deployability, especially when new standards are implemented during the device's lifetime.
Innovation Solution
A method involving an operating system dataset with a previous and updated executable data subset is used to update secure elements, ensuring compatibility by checking data formats before access and allowing updates without altering stored data, enabling future-proof functionality and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If firmware updates are performed on secure elements to implement new standards, then functionality and security are improved, but the risk of version mismatch between operating system and secure element increases
Solution Approach 1:
The operating system dataset includes a version checking mechanism that verifies the secure element's firmware version before and after updates. This feedback loop ensures the OS and secure element remain synchronized, preventing version mismatches while allowing functionality to be updated through controlled update processes.
Solution Approach 2:
The system performs preliminary version verification before executing firmware updates. The operating system dataset checks the current secure element version and validates compatibility before applying updates, ensuring that version consistency is maintained proactively rather than reactively.
2Reliability
If secure elements are updated with new firmware versions, then security is improved, but data format compatibility issues may arise
Solution Approach 1:
The operating system dataset includes data format adaptation mechanisms that automatically adjust to different secure element firmware versions. When a secure element is updated, the OS dataset modifies its data format parameters to maintain compatibility, allowing security improvements without sacrificing data format compatibility.
3Ease of manufacture
If embedded secure elements are updated over-the-air, then deployability is improved, but the complexity of ensuring update integrity increases
Solution Approach 1:
The operating system dataset acts as an intermediary between the update delivery system and the secure element. It receives update packages, verifies their integrity using embedded validation mechanisms, and coordinates the update process, thereby simplifying OTC deployment while maintaining update integrity through a centralized verification point.
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 providing a secure element (6) of the user device (5), such as an eUICC, with an operating system dataset (O) for operating the secure element (6), the operating system dataset (O) comprising a previous version (A) of at least one executable data subset (E) defining a former version (X) of an application process (C) configured to access at least one data object (D) having a predefined data format (M); sending an update data subset (F) to the secure element (6) comprising a following version (B) of the at least one executable data subset (E) defining a later version (Y) of the application process (C) configured to access the at least one data object (D); and installing the following version (B) of the at least one executable data subset (E) on the secure element (6) such that the later version of the application process (C) can be executed, are performed; wherein when the later version of the application process (C) can be executed, an operating instance (V) implemented by the operating system dataset (O) checks whether the predefined data format (M) of the at least one data object (D) matches a required data format (N) defined by the later version of the application process (C) before accessing the at least one data object (D) with the later version (Y) of the application process (C).