Personalized Profile Generation for eUICC Using Master Data Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for generating personalized profile package data for integrated circuit cards, such as eUICC, face inefficiencies due to the need to store and transfer profiles as if they are completely different, despite sharing 95-98% of data, and are limited by maximum profile size and loading time constraints.
Innovation Solution
The method involves creating a table of data records with personalization fields, combining these records with a pre-stored master profile using type-length-value coding, and transmitting encoded data with an offset table to the integrated circuit card, allowing for efficient storage and transfer of personalized profiles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If profiles are stored and transferred as completely different data sets, then each profile can be independently personalized, but the output file size increases and transfer efficiency decreases
Solution Approach 1:
The profile data is segmented into a master profile (containing common 95-98% data) and personalized profile packages (containing only unique personalization fields). This segmentation allows the system to separate the large common data portion from the small variable portions, enabling efficient storage and transfer while maintaining full personalization capability for each profile.
Solution Approach 2:
Instead of transferring complete duplicate profiles, the system uses a master profile as a template and creates personalized copies by inserting only the unique personalization data into specific offset positions. This copying approach dramatically reduces the amount of data that needs to be stored and transferred while preserving the ability to generate complete personalized profiles on the eUICC side.
2Reliability
If complete profiles are transferred to ensure data integrity, then reliability is maintained, but loading time increases due to larger data volume
Solution Approach 1:
The system extracts only the essential personalization fields from complete profiles and stores them in personalized profile packages. The master profile remains on the server side, and only the extracted personalization data (along with offset information) is transferred to the eUICC. This extraction process maintains data integrity for the critical personalization elements while dramatically reducing transfer and loading time.
Solution Approach 2:
The master profile is prepared and validated in advance on the server side before personalization. This preliminary preparation ensures that the base profile structure is reliable and intact, allowing the system to then efficiently transfer only the personalization increments needed to complete each profile, thereby maintaining reliability while minimizing transfer time.
3Quantity of substance
If maximum profile size is increased to accommodate more data, then more information can be stored, but loading time and processing complexity increase
Solution Approach 1:
The system introduces a new dimensional approach by separating profile data into two layers: a static master profile layer stored on the server and a dynamic personalization layer stored on the eUICC. This dimensional separation allows the system to maintain large overall profile capacity through the master profile while keeping the eUICC storage and loading requirements minimal, as only the small personalization increment needs to be transferred and loaded.
Data Source
AI summary
In an embodiment a method includes providing a table including a plurality of data records (R1 . . . Rn) corresponding to a plurality of profile data, providing a master profile including fields to be personalized (F1 . . . Fk . . . Fp) corresponding to one or more of the data records (R1 . . . Rn) to store the different types of personalization values (V1 . . . Vm), combining the one or more of the data records (R1 . . . Rn) in the table with the master profile by inserting the personalization values (V1 . . . Vm) in the fields to be personalized (F1 . . . Fk . . . Fp) to obtain respective personalized profile packages, coding the one or more of the data records (R1 . . . Rn) to obtain encoded data records (CRi), applying the coding to the offset table to obtain encoded data offset (COi) and combining for each record (Ri) the encoded data record (CRi) and the data offset (OCi) in an encoded personalization record (URi).