eUICC On-Board Key Generation for Secure Profile Provisioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for provisioning profiles to eUICCs are vulnerable to unauthorized key sharing, leading to the risk of profile distribution to non-authorized devices, particularly in consumer and IoT eUICCs.
Innovation Solution
Generate network authentication keys on-board in the target eUICC, enabling late profile generation and individualization, thereby preventing clone distribution and key leakage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If profile data including authentication key K is pre-provisioned to eUICC in early stages, then profile assignment is simplified, but security is compromised due to vulnerability to unauthorized key sharing and clone distribution
Solution Approach 1:
The patent applies preliminary action by pre-generating authentication keys K within the eUICC itself, rather than pre-provisioning complete profile data. The eUICC generates its own unique authentication key K during manufacturing or first activation, which is then used to securely download and bind profile data. This preliminary key generation within the secure element eliminates the security vulnerability of transmitting authentication keys externally while still enabling simplified profile assignment.
Solution Approach 2:
The patent introduces an intermediary mechanism where the eUICC's own generated authentication key K acts as a mediator between the profile server and the profile data. Instead of directly sharing authentication keys with external entities, the eUICC uses its internally generated key K to authenticate and bind profile data during the download process. This intermediary key generation within the secure element prevents unauthorized key sharing while enabling secure profile provisioning.
2Productivity
If authentication keys are shared externally for profile generation, then profile distribution is efficient, but key leakage and unauthorized cloning risks increase
Solution Approach 1:
The patent extracts the authentication key generation function from external systems and places it exclusively within the eUICC. Instead of sharing authentication keys externally for profile generation, the eUICC independently generates its own authentication key K and uses this key to securely receive and bind profile data from the profile server. This extraction of key generation to the secure element eliminates key leakage risks while maintaining efficient profile distribution through secure key-bound downloads.
Solution Approach 2:
The patent applies self-service by enabling the eUICC to autonomously generate its own authentication key K without requiring external key provisioning. The eUICC independently creates its unique key K, uses it to authenticate with the profile server, and binds profile data to this key. This self-generated key approach eliminates the need for external key sharing while maintaining efficient profile distribution, as the eUICC serves itself with authentication credentials.
3Reliability
If profile data is bound to specific eUICC using external keys, then profile security is enhanced, but key management complexity increases
Solution Approach 1:
The patent merges the authentication key generation and profile binding functions into a single integrated process within the eUICC. Instead of managing separate external authentication keys and profile binding mechanisms, the eUICC generates its own authentication key K and uses this same key for both authentication and profile binding. This merging of functions within the secure element enhances profile security through strong key binding while simplifying key management by eliminating external key infrastructure.
Data Source
Figure 1
Figure 2
AI summary
A method for establishing, in a target eUICC, profile data of at least one profile, the profile data including at least an authentication key K, the method comprising the step: a) receive at the eUICC MNO information including at least an indication which profile data shall be generated; the method characterized by the step performed after step a): b) generate, in the target eUICC, at least some of the profile data, herein at least a network authentication key K; c) after step b) export the profile data generated in the target eUICC, or at least part thereof, from the target eUICC to an external entity; d) receive at the external entity at least some or all of the exported profile data, herein at least the authentication key K; and e) initiate generation of a profile including the received authentication key, at the external entity, or at an entity called by the external entity.