Embedded UICC Test Profile Updates with Compact File Instructions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for modifying a test profile in integrated circuit cards, such as UICC and eUICC, lack clear guidance on how to update Elementary File Test files, leading to inefficiencies in device testing processes.
Innovation Solution
A method for updating test profiles in integrated circuit cards using a Test Applet that employs a file path concatenation to identify target files and updates file contents with significant data and a filling pattern, ensuring efficient and space-saving modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If complete file content transfer is used to update test profile files, then file update reliability is improved, but data transmission time and storage requirements increase
Solution Approach 1:
The patent extracts only the essential parts of file content (significant data) that need to be updated, rather than transferring complete file contents. The Elementary File Test file stores compact update instructions including file paths, significant data portions, and filling patterns, which are then applied to generate updated target files during testing operations.
Solution Approach 2:
Instead of storing and transferring complete file contents for updates, the patent inverts the approach by storing only the differences and essential update information. The Elementary File Test file contains concise update instructions that reference target files and specify what changes to apply, rather than containing the full target file contents themselves.
2Reliability
If complete file content is stored in test profile, then file update completeness is improved, but storage space requirements increase
Solution Approach 1:
The patent extracts and stores only the significant data portions that are essential for file updates, rather than storing complete file contents. The Elementary File Test file contains compact update instructions with file paths, significant data, and filling patterns, minimizing storage requirements while maintaining update completeness.
Solution Approach 2:
The patent performs preliminary organization of update information in the Elementary File Test file during profile setup. File paths, significant data, and filling patterns are pre-structured and stored in an optimized format, enabling efficient space utilization while ensuring all necessary update information is available when needed.
3Measurement precision
If detailed file path information is stored, then file identification accuracy is improved, but data structure complexity increases
Solution Approach 1:
The patent segments file path information into hierarchical components (parent file identifiers and target file identifiers) that are concatenated to form complete paths. The Elementary File Test file structure divides update information into distinct records with standardized fields, organizing complex path data into manageable segments that improve identification accuracy while maintaining structural clarity.
Solution Approach 2:
The patent creates a universal data structure in the Elementary File Test file that handles multiple file identification scenarios through a consistent format. The same record structure accommodates different file paths, target files, and update types, providing a multi-functional solution that maintains accuracy without proportionally increasing complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Method for modifying a test profile in an integrated circuit card, in particular an embedded UICC, (108), to test an apparatus (10), in particular a device, hosting said integrated circuit card (108), said method comprising using as test profile a generic test profile (GTP) stored in said integrated circuit card (108) comprising an Elementary File Test file (EFT) containing information for updating files in order to support apparatus test operations and a test applet (TAP) configured to perform said updating on files of said generic test profile (GTP), said test applet (TAP) being configured to perform an update operation (335) on contents of a target elementary file (TGF) with a determined file identifier (<File Id>), storing in a record of the Elementary File Test file (EFT) information to perform said operation of update ((<File Path>), <data to be updated>), said information to perform said operation of update in a record of the Elementary File Test file (EFT) ((<File Path>), <data to be updated>) comprising a file path (<File Path>) identifying the position of said target elementary file (TGF) with a determined file identifier (<File Id>) in the file system (FS) of the Elementary File Test file (EFT), obtained as the concatenation of a respective parent file identifier in the file system (FS) of the Elementary File Test file (EFT) followed by the target Elementary File (TGF) file identifier (<File Id>), data to be updated <data to be updated>) built as comprising a first type of data (SD) corresponding to significant data, preceded by a length indication of the first type of data (SD), and a second type of data corresponding not significant data, represented as a filling pattern (FP), in particular preceded by length indication of the second type of data (SD), reading (330) by the Test Applet (TAP) said information to perform said operation of update in a record of the Elementary File Test file (EFT) ((<File Path>), <data to be updated>) stored, performing (335) said operation of update by selecting the target elementary file (TGF) in the file system (FS) of the Elementary File Test file (EFT) by said file path (<File Path>) and updating its content with said significant data (DS) and said filling pattern (FP) used in one or more instances to fill the target elementary file (TGF) until the end of its size.