eSIM Profile Transfer Using Post-Deletion Key Release
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing GSMA security protocol for eSIM profiles prevents the transfer of eSIM data between devices without the risk of cloning, as the eUICC never exposes decrypted data, limiting flexibility and security.
Innovation Solution
A method where profile encryption keys are generated on the exporting eUICC device, stored until the profile is deleted, and then sent to the target device for decryption, ensuring the profile is only present on one entity at a time, preventing cloning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If eSIM profile data is transferred using conventional one-way-street protocol, then security is maintained through encryption, but flexibility and ability to transfer profiles between devices is lost
Solution Approach 1:
The exporting eUICC device deletes the eSIM profile data before transferring the decryption keys to the target entity. This preliminary deletion action ensures that the profile cannot be cloned during transfer, while still enabling flexible profile movement between devices.
Solution Approach 2:
Instead of the conventional approach where the receiving entity decrypts data received from the sending entity, this patent inverts the process: the sending entity deletes its data first, then transfers only the decryption keys, allowing the receiving entity to decrypt what it receives without the sender ever having exposed the decrypted profile.
2Ease of operation
If eSIM profile data is stored and decrypted on the exporting eUICC device, then profile management is simplified, but security against cloning is compromised
Solution Approach 1:
The exporting eUICC device performs deletion of the eSIM profile data as a preliminary action before transferring decryption capabilities. This eliminates the cloning risk while maintaining simplified profile management through automated key transfer.
Solution Approach 2:
The patent extracts the decryption keys from the encrypted profile data and transfers only these keys to the target entity. The actual profile data remains encrypted and is decrypted only at the receiving end, preventing exposure and cloning during transfer.
3Quantity of substance
If eSIM profile data is transferred in streaming mode, then resource constraints of eUICC are respected, but security control over the transfer process is reduced
Solution Approach 1:
The deletion of profile data is performed as a preliminary action before key transfer, regardless of whether the transfer occurs in streaming mode or not. This maintains security control while respecting the resource constraints that necessitate streaming transfer.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
Method for transferring eSIM profile data (30) from a first eUICC device (210) to a target entity, comprising the steps: a. providing encrypted eSIM profile data (30) on the first eUICC device (110), the encrypted eSIM profile data (30) having been encrypted by means of profile encryption keys (20); b. transferring the encrypted eSIM profile data (30) from the first eUICC device (110) to the target entity; c. deleting the encrypted eSIM profile data (30) from the first eUICC device (110); d. transferring the profile data encrypting keys (20) from the first eUICC device (110) to the target entity only after completion of steps b. and c.; and e. decrypting the encrypted eSIM profile data (30) by means of the profile encryption keys (20) and installing the decrypted eSIM profile data (30) on the target entity.