eUICC Context Switching Without Full Resets for Consumer and IoT eSIMs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current eUICC technologies are limited to managing a single context (consumer or IoT) at a time, requiring a full reset to transition between contexts, leading to operating inefficiencies and communication outages.
Innovation Solution
A method for concurrently managing consumer and IoT contexts by providing a terminal capability command to an eUICC, allowing it to process function calls and responses for both consumer-related and IoT-related eSIMs simultaneously.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a eUICC manages a single context (consumer or IoT) at a time, then the device complexity is reduced and ease of operation is improved, but the adaptability and productivity deteriorate because the eUICC cannot handle both consumer and IoT functionalities simultaneously
Solution Approach 1:
The eUICC is divided into multiple independent context instances (consumer context and IoT context), each capable of operating independently with its own eSIM profiles and functionality. This segmentation allows the eUICC to manage multiple contexts simultaneously without interference, resolving the contradiction between adaptability and productivity.
Solution Approach 2:
The eUICC is designed to perform multiple functions by supporting both consumer and IoT contexts within a single device. The universal architecture allows the eUICC to handle diverse functionalities (telephony, messaging, IoT diagnostics, location services) simultaneously, improving both adaptability and operational efficiency.
2Adaptability or versatility
If the eUICC transitions between contexts using a full reset, then the context switching is completed, but the loss of time increases and reliability decreases due to operating inefficiencies and communication outages
Solution Approach 1:
The eUICC implements dynamic context switching without requiring a full reset. The system can transition between consumer and IoT contexts dynamically based on operational needs, maintaining continuous service availability and eliminating time losses associated with resets.
Solution Approach 2:
The eUICC maintains continuous operational capability by allowing context switching without interruption. The useful action (service provision) continues uninterrupted during context transitions, preventing communication outages and eliminating time losses.
3Reliability
If the eUICC performs full reset to transition between contexts, then the context is properly switched, but the reliability and productivity worsen due to operating inefficiencies and communication outages
Solution Approach 1:
The eUICC prepares context switching in advance by maintaining multiple context instances ready for immediate activation. This preliminary preparation eliminates the need for disruptive resets, ensuring service continuity and maintaining high operational efficiency.
Solution Approach 2:
The system introduces a context management intermediary layer that handles transitions between consumer and IoT contexts. This intermediary enables smooth switching without requiring full resets, maintaining both reliability and productivity by preventing service interruptions.
Data Source
AI summary
This application sets forth techniques for managing both consumer and Internet of Things (IoT) contexts relative to utilizing at least one consumer-related electronic Subscriber Identity Module (eSIM) and at least one IoT-related eSIM, respectively. According to some embodiments, the method can be implemented by a wireless device, and includes providing, to an embedded Universal Integrated Circuit Card (eUICC) included in the wireless device, a terminal capability command that indicates both the consumer and IoT contexts should be managed. In turn, the wireless device can provide function calls to the eUICC, where the function calls are accompanied with context information to indicate the context (i.e., consumer or IoT) under which the function calls should be processed. Additionally, the wireless device can provide context switch (i.e., consumer or IoT) commands to the eUICC, to cause the eUICC to utilize a particular context when processing function calls (until further notice is received).


