eUICC Profile Loading via Executable BLOB
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for loading a subscription profile into a subscriber identity module require significant data transmission over-the-air (OTA) due to the need for multiple specific commands like 'Create', 'Update', and 'Enable', resulting in excessive data being sent, especially when updating or changing profiles.
Innovation Solution
Loading the profile as a single executable program code module that is executed upon receiving a communication APDU command, eliminating the need for separate installation commands, and utilizing a Binary Large Object (BLOB) or Java applet to install the profile within the subscriber identity module.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple specific installation commands (Create, Update, Enable) are sent to the subscriber identity module, then the profile can be properly installed and activated, but the amount of data transmitted OTA increases significantly
Solution Approach 1:
The patent combines multiple separate installation commands (Create, Update, Enable) into a single integrated loading command. Instead of transmitting three separate commands with their respective parameters, the system transmits one unified command that performs all installation steps atomically, thereby reducing OTA data transmission volume while maintaining complete profile installation functionality
Solution Approach 2:
The loading command is designed with multi-functionality to perform multiple operations (creation, updating, and enabling of profile) within a single command structure. This universal command can handle different installation scenarios (new profile, profile update, profile activation) without requiring separate specialized commands, thus reducing the overall data transmission requirement
2Ease of operation
If multiple separate commands are used for profile installation, then each installation step can be controlled individually, but the complexity of the installation process increases
Solution Approach 1:
The patent merges the complex sequence of multiple commands (Create, Update, Enable) into a single unified loading command. This eliminates the need for the system to process and coordinate multiple separate commands, thereby simplifying the installation process and reducing operational complexity while maintaining all necessary installation steps within the single command
3Reliability
If traditional profile loading methods are used, then compatibility with existing systems is maintained, but the efficiency of subscription management decreases
Solution Approach 1:
The patent changes the parameter structure of the installation command from multiple separate commands with individual parameters to a single command with a consolidated parameter set. This parameter transformation maintains compatibility with existing command interfaces while significantly improving subscription management efficiency by reducing the number of transmission and processing operations required
Data Source
Figure 1
Figure 2
AI summary
The invention relates to a method for loading a profile (P1) for a mobile communication subscription from a data processing server (SM-DP) into a subscriber identity module (eUICC), having the following steps: a) providing a profile (P1) in the data processing server (SM-DP); b) generating an individual executable program code module (BLOB) of the profile (P1) provided in step a), said module being designed such that the profile (P1) is installed into the subscriber identity module (eUICC) by executing the executable program code module (BLOB); and c') loading the individual executable program code module (BLOB) into the subscriber identity module (eUICC). The invention further relates to a method for installing a profile (P1) loaded according to claim 1 into the subscriber identity module (eUICC), having the following steps: d) transmitting an APDU command from the data processing server (SM-SP) to the subscriber identity module (eUICC); and e) in response to receiving the APDU command in the subscriber identity module (eUICC), executing the executable program code module (BLOB) and installing the profile (P1) into the subscriber identity module (eUICC) by means of the execution of the program code module.