IoT eSIM Orchestration Hub for Synchronized Subscription Distribution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote SIM provisioning (RSP) technologies face challenges in synchronizing operations with device availability, including subscription context information, accessing RSP servers without internet connectivity, and enabling local profile management for IoT devices, which are not adequately addressed by GSMA standards SGP.02, SGP.22, and SGP.32.
Innovation Solution
An orchestration hub system that connects to device and connectivity management systems, synchronizes network subscription information, and manages eSIM profiles with multiple IMSIs, allowing for centralized management and local profile updates via APDU messages, and supports campaign-based operations for efficient management of IoT devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If existing RSP standards (SGP.02, SGP.22, SGP.32) are used for IoT devices, then basic eSIM profile download is enabled, but synchronization with device availability and subscription context information delivery cannot be achieved
Solution Approach 1:
The system implements feedback mechanisms where the RSP server receives status information from IoT devices about their availability and operational state. This feedback loop enables the server to synchronize profile downloads and subscription context deliveries with actual device availability, ensuring reliable delivery without requiring continuous device presence.
Solution Approach 2:
The system performs preliminary actions by pre-downloading and caching eSIM profiles and subscription context information on the RSP server before devices need them. When devices become available, the pre-prepared information is immediately transferred, eliminating waiting time and ensuring synchronous operation without requiring real-time device connectivity.
2Adaptability or versatility
If RSP servers are accessed via traditional internet connectivity, then standard provisioning is enabled, but access cannot be provided when internet is not available
Solution Approach 1:
The system introduces alternative communication channels as intermediaries between IoT devices and the RSP server. When internet connectivity is unavailable, the system uses local messaging queues, Bluetooth Low Energy (BLE) communication, or other short-range wireless protocols as intermediary channels to maintain provisioning capability, ensuring the system adapts to various connectivity conditions.
Solution Approach 2:
The system dynamically changes the communication parameters and protocols used for RSP operations based on available connectivity conditions. When internet is unavailable, the system switches from HTTP/HTTPS protocols to alternative protocols such as CoAP over UDP, MQTT over WebSocket, or direct device-to-device communication, maintaining provisioning reliability across different network environments.
3Device complexity
If centralized RSP management is implemented, then subscription management is simplified, but local profile management capability is not enabled
Solution Approach 1:
The system segments the RSP management function into two independent parts: a centralized RSP server that handles high-level subscription management and profile selection, and a local device agent that handles actual profile installation and local modifications. This segmentation allows centralized simplification of subscription management while preserving local profile management capability through the distributed device agent.
Solution Approach 2:
The system merges centralized and local management capabilities into a unified architecture where the RSP server and device agents work together seamlessly. The server provides centralized subscription context and profile information, while device agents locally install and manage profiles. The two layers are merged through standardized communication protocols, enabling both centralized simplification and local management flexibility simultaneously.
4Productivity
If traditional RSP processes are used for large-scale IoT deployments, then basic connectivity provisioning is achieved, but operational efficiency and cost management are insufficient
Solution Approach 1:
The system implements continuous background processes that automatically synchronize device status information with the RSP server, continuously monitor provisioning states, and maintain updated profiles without requiring manual intervention. This continuous operation ensures high productivity in large-scale deployments while minimizing management operation time through automated workflows that run continuously rather than periodically.
Solution Approach 2:
The system enables self-service operations where IoT devices automatically report their availability status, the RSP server automatically selects appropriate profiles, and devices automatically install and activate profiles without human intervention. This self-service capability dramatically improves provisioning efficiency for large-scale deployments while reducing management operation time to only essential monitoring and exception handling tasks.
Data Source
AI summary
Systems, processes, and apparatuses are disclosed including an orchestration agent and an orchestration hub. The orchestration agent is operatively connected to an eUICC and memory at a mobile computing device. The orchestration hub includes a processor and a database including centralized network subscription information. The orchestration hub can receive updated network subscription information from a device management and from a network connectivity management platform. The orchestration hub can compare the updated network subscription information to a plurality of subscription records in the centralized network subscription information. The orchestration hub generates a new subscription record including current network subscription information based on the updated network subscription information. The orchestration agent can replace one or more information fields of a subscription edge record at the eUICC and the memory with corresponding information fields from the new subscription record.