eUICC File System Management for Dynamic eSIM Profile Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy file systems for removable Universal Integrated Circuit Cards (UICCs) mix hardware-specific and MNO-specific information, making it challenging to manage eSIM profiles and maintain backward compatibility with external processing modules in embedded UICCs, which require flexible eSIM profile management and increased flexibility.
Innovation Solution
A dynamic file system management method for embedded UICCs that separates hardware-specific and MNO-specific information, allowing for the creation, storage, and updating of customized eUICC level files based on eSIM changes, such as enabling, disabling, or updating eSIMs, by merging default eUICC files with MNO-specific information from eSIMs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a legacy file system mixing hardware-specific and MNO-specific information is used for removable UICCs, then backward compatibility with external processing modules is maintained, but flexibility for eSIM profile management in embedded UICCs is reduced
Solution Approach 1:
The file system is segmented into two distinct parts: a hardware-specific file system portion that maintains backward compatibility with external processing modules, and an MNO-specific file system portion that enables flexible eSIM profile management. This segmentation allows each part to serve its specific function independently without compromising the other.
Solution Approach 2:
MNO-specific information is extracted from the traditional mixed file system and placed into a separate, dedicated file system structure. This extraction allows the hardware-specific portion to remain unchanged for compatibility purposes, while the MNO-specific portion can be dynamically modified for eSIM profile management.
2Adaptability or versatility
If a static file system structure is used for eUICCs, then simplicity of implementation is maintained, but ability to dynamically manage multiple eSIM profiles is reduced
Solution Approach 1:
The file system structure transitions from a static to a dynamic configuration, where MNO-specific information can be added, removed, or modified based on eSIM profile changes. The system automatically adapts the file system structure in response to eSIM installation, enabling, disabling, or removal events.
Solution Approach 2:
The file system management system incorporates feedback mechanisms that monitor eSIM state changes and automatically trigger appropriate file system updates. When an eSIM is installed, enabled, disabled, or removed, the system receives feedback about the state change and dynamically adjusts the file system structure accordingly.
3Adaptability or versatility
If MNO-specific information is integrated into the hardware-specific file system, then unified file management is achieved, but ability to maintain compatibility while supporting multiple MNOs is reduced
Solution Approach 1:
The file system is divided into distinct segments: one dedicated to hardware-specific information and another for MNO-specific information. This segmentation allows the system to support multiple MNOs by loading different MNO-specific file portions while maintaining a consistent hardware-specific foundation, making multi-MNO support more manageable.
Solution Approach 2:
The hardware-specific file system portion serves as a universal foundation that works with multiple different MNO-specific configurations. This universal structure enables the same hardware file system to support multiple MNOs by simply changing the MNO-specific portion, enhancing ease of operation across different network operators.
Data Source
AI summary
Methods and apparatus for dynamic file system management of an embedded Universal Integrated Circuit Card (eUICC) in response to changes for electronic Subscriber Identity Modules (eSIMs) on the eUICC are disclosed herein. Hardware specific file information, e.g., hardware-based eUICC parameters, which may apply to multiple eSIMs and/or multiple Mobile Network Operators (MNOs), is included in a default eUICC file system. MNO specific information, e.g., MNO-specified parameters, is included in eSIMs. Customized eUICC level files are created, stored, modified and/or replaced based on a combination of default eUICC files and MNO specific information extracted from an eSIM at installation and/or in response to a change of state of the eSIM, such as when enabling, disabling, or updating the eSIM on the eUICC.