Secure Element Applet Data Backup and Update
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for managing applets on secure elements face challenges in updating or deleting applets without losing critical data, particularly during periods when managing applets are not fully active, and ensuring that applets receive the most up-to-date critical data post-update.
Innovation Solution
A system that allows applets to establish a shareable interface object (SIO) for data exchange, where a wallet companion applet (WCAp) communicates with a secure assistant applet (ISAp) to store and backup critical data, enabling seamless updates and replacements of applets without data loss, using commands like 'request SIO' and 'put data' to transfer and replace data securely.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If managing applets are altered or deleted to update versions, then applet functionality is improved, but critical data may be lost or left unmanaged
Solution Approach 1:
The system performs preliminary actions by creating a backup applet before deleting or altering the managing applet. The backup applet is instantiated with copied data from the secure element, ensuring critical data is preserved before the original applet is modified or removed. This preliminary backup action prevents data loss during applet updates.
Solution Approach 2:
The system creates a copy of the managing applet (backup applet) and copies the critical data from the secure element to this backup applet. This copying mechanism ensures that even if the original managing applet is deleted or altered, the critical data remains intact in the backup applet, resolving the contradiction between applet update flexibility and data preservation.
2Reliability
If critical data is stored on secure elements with specialized security mechanisms, then data security is improved, but storage cost increases and storage capacity is limited
Solution Approach 1:
The system segments data storage by separating critical data from non-critical data. Critical data is stored on the secure element with specialized security mechanisms, while non-critical data is stored in the application's file system on the mobile device. This segmentation allows the system to maintain high security for essential data without the cost and capacity constraints of storing all data on the secure element.
Solution Approach 2:
The system applies different storage qualities to different data types. Critical data receives the highest security quality through secure element storage, while non-critical data uses standard mobile device storage. This local quality differentiation optimizes the balance between security requirements and storage cost/capacity constraints.
3Adaptability or versatility
If applets are updated or replaced, then functionality is improved, but data integrity management becomes complex during transition periods
Solution Approach 1:
The system introduces a backup applet as an intermediary during the applet update process. This backup applet acts as a temporary mediator that holds critical data while the original managing applet is being updated or replaced. The intermediary backup applet simplifies the transition process by providing a stable data repository during the update period, reducing the complexity of data management during transitions.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Systems, methods, and computer program products are provided for managing applets. A first request to personalize the first applet is received over a communications network. A second request including a command requesting at least a portion of the second applet data is communicated to the second applet. At least a portion of the second applet data is communicated to the first applet. One or more values of the first applet data are replaced with one or more values of at least the portion of the second applet data.