Secure Element Applet Migration Data Preservation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for updating applets on wireless electronic devices face challenges such as data loss and security risks during version migration, and can become bottlenecks when updating multiple devices concurrently.
Innovation Solution
The described solution involves an electronic device with a secure element that receives an update package with a digital signature, identifies and verifies previous applet versions, uninstalls them, exports user data, and installs the new update while personalizing the applet using the user data, utilizing encryption keys for secure operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the old version of the applet is uninstalled or deleted prior to installing the new version, then the new version can be installed, but user data may be lost
Solution Approach 1:
The system performs preliminary actions by exporting user data from the old applet version before uninstallation and storing it in a temporary location. This preliminary data preservation enables the subsequent installation of the new version without data loss, as the data is restored after the new version is successfully installed.
Solution Approach 2:
A data migration mechanism acts as an intermediary between the old and new applet versions. The system exports data from the old version, stores it temporarily in the secure element, and then imports it to the new version. This intermediary data storage mechanism prevents direct data loss during the version transition.
2Reliability
If user data is migrated from the old version prior to installation, then data can be preserved, but security risks increase
Solution Approach 1:
The system extracts user data from the old applet version's secure storage environment and temporarily stores it in a controlled temporary location within the secure element. This extraction is performed under strict security protocols, and the data is immediately re-imported to the new version, minimizing the time data exists in a potentially vulnerable state.
Solution Approach 2:
The system implements beforehand cushioning by maintaining data within the secure element's protected environment throughout the migration process. The secure element's hardware-based security boundaries cushion the data from external threats, and cryptographic protections are applied to prevent unauthorized access during the transition.
3Productivity
If the server is used to update applets on many electronic devices concurrently, then updates can be distributed, but the server becomes a bottleneck
Solution Approach 1:
The update distribution system is segmented into multiple components: a headend system that prepares update packages, electronic devices that receive and process updates, and a data migration subsystem. This segmentation allows parallel processing of updates across multiple devices without requiring a single centralized server to handle all operations sequentially, reducing the bottleneck effect.
Solution Approach 2:
The electronic devices perform self-service during the update process by automatically receiving update packages, uninstalling old versions, migrating their own data, and installing new versions without requiring continuous server intervention. This self-service capability reduces the load on the server and enables concurrent updates across multiple devices.
Data Source
AI summary
An electronic device (such as a cellular telephone) automatically installs and personalizes updates to an applet on a secure element in the electronic device. In particular, when a digitally signed update package containing the update is received from an updating device (such as a server), the secure element identifies any previous versions of the applet installed on the secure element. If there are any previously installed versions, the secure element verifies the digital signature of the update package using an encryption key associated with a vendor of the secure element. Then, the secure element uninstalls the previous versions of the applet and exports the associated user data. Next, the secure element installs the update to the applet, and personalizes the new version of the applet using the user data.