eUICC Profile Provisioning With Identifier Checks Against Cloning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In existing eUICC profile provisioning methods, particularly in-factory provisioning, there is a risk of profiles being downloaded to the wrong eUICC or multiple eUICCs due to encryption with the same key, leading to potential cloning issues.
Innovation Solution
Implementing a provisioning profile with a profile enabler in the eUICC that verifies the profile identifier against an expected identifier from an enablement orchestration server, ensuring that profiles are enabled only when matching identifiers are confirmed, and disabling the provisioning profile if more than one enabled profile is not allowed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If profiles are encrypted with the same key for batch provisioning, then provisioning efficiency is improved, but security and reliability deteriorate due to risk of downloads to wrong eUICCs and cloning
Solution Approach 1:
The patent applies local quality by making each profile encryption key unique to a specific eUICC device. Instead of using a single shared key for batch provisioning, the system generates individual encryption keys for each eUICC based on device-specific identifiers. This ensures that while batch provisioning remains efficient, each profile is securely bound to its intended target device, preventing accidental downloads to wrong eUICCs and eliminating cloning risks.
2Reliability
If profile identifiers are verified against expected identifiers, then profile installation reliability is improved, but device complexity increases due to additional verification mechanisms
Solution Approach 1:
The patent implements preliminary action by pre-registering the expected profile identifier and associated eUICC identifier in an enablement orchestration server before the actual profile download occurs. When a profile is downloaded, the eUICC automatically performs verification by comparing the downloaded profile identifier against the pre-registered expected identifier. This approach ensures high installation reliability while keeping the verification mechanism simple and automated, avoiding complex runtime decision-making.
3Reliability
If provisioning profiles are disabled after profile installation, then security is improved by preventing unauthorized enabling, but ease of operation deteriorates due to additional management steps
Solution Approach 1:
The patent applies feedback by implementing an automatic status update mechanism. When a profile is successfully installed and verified on an eUICC, the enablement orchestration server automatically receives notification and updates the provisioning profile status to disabled. This feedback loop ensures that provisioning profiles are automatically secured after use without requiring manual intervention, maintaining both high security and operational simplicity.
Applied Scientific Principles
This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.
Function Achieved in This Case
Ensures reliable and secure installation of profiles by preventing accidental downloads to incorrect eUICCs and preventing cloning, thereby enhancing the integrity of profile provisioning.
Implementation Method 1
an Elliptic Curve Key Agreement Algorithm (ECKA) is used for the establishment of a shared secret value
Implementation Method 2
the profile enabler is constructed to perform steps: E1) receive from the target profile the profile identifier; E2) receive from an enablement orchestration server an expected profile identifier of a profile installed in the eUICC; E3) enable the target profile only under the condition that the profile identifier and the expected profile identifier match with each other
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An eUICC comprising - a provisioning profile (P1) installed in the eUICC (10), and constructed for provisioning of profiles installed or scheduled to be installed in the eUICC (10); - at least one profile, referred to as target profile (P2), installed in the eUICC (10) including a profile identifier (ID), and present in a disabled status; characterized in that - the provisioning profile (P1) comprises a profile enabler (PE) constructed to perform steps: -- E1) receive from the target profile (P2) the profile identifier (ID); -- E2) receive from an enablement orchestration server (20) an expected profile identifier (IDe) of a profile installed in the eUICC; -- E3) enable the target profile (P2) only under the condition that the profile identifier (ID) retrieved from the target profile (P2) and the expected profile identifier (IDe) retrieved from the enablement orchestration server (20) match with each other; - and optionally, when enabling the target profile (P2), disable the provisioning profile (P1).