MQTT-Based Client-Centric eSIM Provisioning for Concurrent IoT Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing remote SIM provisioning methods for IoT devices with eSIMs are inefficient and time-consuming, particularly when bulk profile changes or client-centric provisioning is required, such as in device replacements due to malfunctions, and do not effectively support large-scale, concurrent provisioning.

Innovation Solution

A method and apparatus for bidirectional profile provisioning using a message queueing telemetry transport (MQTT) protocol to enable client-centric and concurrent provisioning, allowing devices to initiate profile requests and changes directly, rather than relying solely on server-centric methods, with a provisioning control unit determining the initiator and direction of provisioning.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional server-centric RSP provisioning is used, then profile installation can be performed on IoT devices, but the process is time-consuming and inefficient for bulk or client-centric provisioning scenarios

Engineering Contradiction:
Improveprofile provisioning speedVSAvoidtime for secure channel setup and profile download
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent inverts the conventional server-centric provisioning model by enabling client-centric provisioning where the IoT device initiates the provisioning process and requests profiles from the server. This inversion allows devices to autonomously trigger provisioning events, eliminating the need for repetitive server-initiated secure channel setups and significantly reducing provisioning time for bulk operations and device replacements

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent implements preliminary action by establishing persistent connections and pre-configuring provisioning parameters before actual profile installation is needed. Devices maintain ready-state communication channels with provisioning servers, so when provisioning is required, the time-consuming secure channel setup has already been completed, enabling immediate profile deployment

Inventive Principle:
Principle #10Preliminary action

2Productivity

If conventional RSP protocol is used, then individual device provisioning can be performed, but bulk provisioning and concurrent provisioning operations are inefficient and require repetitive tasks

Engineering Contradiction:
Improvebulk provisioning efficiencyVSAvoidrepetitive provisioning tasks for multiple devices
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges multiple individual provisioning operations into a single concurrent operation by enabling the provisioning server to establish one secure channel that can serve multiple devices simultaneously. The server can broadcast profile data to multiple subscribed devices through this single channel, combining what would traditionally require multiple separate provisioning sequences into one unified operation

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements universality by designing a provisioning system where a single provisioning server instance can handle multiple types of provisioning scenarios (individual provisioning, bulk provisioning, client-centric provisioning, server-centric provisioning) through a unified MQTT-based architecture. The system universally supports both push and pull provisioning models, making the infrastructure adaptable to various deployment scenarios without requiring separate systems

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If server-centric provisioning is used, then profiles can be pushed to devices, but client-centric provisioning needs such as device replacement cannot be efficiently addressed

Engineering Contradiction:
Improvesupport for client-centric provisioning scenariosVSAvoidability to initiate provisioning from device side
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements dynamics by making the provisioning initiation direction flexible and changeable. The system can dynamically switch between server-centric push mode and client-centric pull mode based on operational requirements. Devices can dynamically subscribe to provisioning topics and autonomously initiate profile requests, while servers can dynamically publish profiles to topics that devices are monitoring, allowing the system to adapt its provisioning direction in real-time

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20250267436A1Method and apparatus for client-centric remote profile provisioning on m2m IoT devices supporting esim
Publication Date: 2025.08.21 ELECTRONICS & TELECOMM RES INST
  • US20250267436A1 patent drawing
  • US20250267436A1 patent drawing
  • US20250267436A1 patent drawing

AI summary

Provided is a method and apparatus for remote profile provisioning for an Internet of Things (IoT) device supporting an e-subscriber identity module (eSIM). The method and apparatus perform bidirectional profile provisioning for machine to machine (M2M) IoT devices. The present invention does not unilaterally perform server-centric provisioning on a client, but uses a newly designed message type and format for client-centric provisioning and concurrent provisioning, in consideration of the initiator and direction of provisioning and the need for concurrent provisioning.