eUICC Profile Deletion via Master Delete Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing eUICC technology lacks a secure and user-controlled method to delete profiles, particularly those set with 'Do Not Delete' and 'Do Not Delete on Reset' policies, which can lead to devices being locked to specific networks or becoming inaccessible if the original MNO goes out of business or if a user wants to change service providers.
Innovation Solution
Introducing a Device-Specific Master Delete Key (MDK) that allows the device owner to delete profiles, including those set with profile policy rules (PPR2 and PPR4), with multiple MDKs providing different levels of profile-deletion access, and utilizing a blockchain for secure key transfer and storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If profile policy rules (PPR2 and PPR4) are set to prevent deletion, then network security and service stability are improved, but device flexibility and user control are worsened
Solution Approach 1:
The patent segments the delete key functionality into multiple types: regular delete keys for normal profile deletion, and master delete keys for bypassing PPR2 and PPR4 restrictions. This segmentation allows the system to maintain profile protection for regular operations while providing elevated access for legitimate override scenarios, thus resolving the contradiction between security and flexibility.
Solution Approach 2:
The patent applies different deletion permissions to different profiles based on their PPR settings. Profiles with PPR2 and PPR4 have restricted deletion access, while profiles without these restrictions allow normal deletion. This local differentiation enables the system to maintain security where needed while preserving flexibility where appropriate.
2Adaptability or versatility
If multiple profiles are stored on eUICC, then service provider options are improved, but risk of unauthorized access and profile locking is worsened
Solution Approach 1:
The patent implements preliminary security measures by requiring authentication with appropriate delete keys before any profile deletion operation. The system preemptively establishes access control mechanisms that prevent unauthorized deletion attempts, thus allowing multiple profiles to coexist securely without risking unauthorized access or profile locking.
Solution Approach 2:
The patent introduces delete keys and master delete keys as intermediary authentication mechanisms between the user and profile deletion operations. These intermediaries verify authorization before allowing profile modifications, thus enabling multiple profiles to be stored and managed securely without exposing the system to unauthorized access risks.
3Ease of manufacture
If eUICC is permanently embedded in device, then manufacturing cost and device integration are improved, but ability to physically swap profiles is worsened
Solution Approach 1:
The patent replaces the mechanical profile swapping mechanism (physical SIM card removal and insertion) with an electronic/software-based mechanism. Profiles can be deleted, activated, and switched through software operations using delete keys and master delete keys, thus maintaining ease of manufacture with embedded eUICC while restoring profile swapping capability through digital means.
Data Source
AI summary
An eUICC is configured with one or more master delete keys each allowing an associated level of profile-deletion access for deleting one or more profiles from the eUICC, and the eUICC is configured to control profile-deletion access in accordance with the one or more delete keys. For instance, one delete key could allow deletion of any or all profiles on the eUICC including any operational profiles (e.g., MNO profiles) and any non-operational profiles. Whereas, another delete key could allow deletion of any or all operational profiles but not any non-operational profiles. Further, a blockchain protocol could be used to securely convey such a delete key from one party to another, helping to establish chain of custody of the delete key.

