Automated Device Bootstrapping via Provisioning Node
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for remote provisioning of cellular connectivity-enabled devices require local storage of expensive provisioning profiles, which is impractical for mass bootstrapping of devices, especially in scenarios where user intervention is not feasible, such as in Machine to Machine (M2M) devices located in remote areas.
Innovation Solution
A method for automated bootstrapping of devices using a provisioning node connected to a subscription manager, where devices send a provisioning profile request, authenticate, and receive a provisioning profile, eliminating the need for pre-installed profiles and user intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a provisioning profile is pre-installed on the device, then the device can be bootstrapped, but the manufacturing cost increases and mass bootstrapping becomes impractical
Solution Approach 1:
The provisioning profile is prepared and stored in advance on a provisioning server rather than being pre-installed on each device. This preliminary action enables mass bootstrapping by allowing multiple devices to download the same profile independently, eliminating the need for costly per-device profile installation during manufacturing.
Solution Approach 2:
A provisioning server acts as an intermediary between the subscription manager and multiple devices. This intermediary stores provisioning profiles and distributes them to devices on demand, enabling efficient mass bootstrapping without requiring direct device-to-subscription-manager communication for each device.
2Ease of operation
If the GSMA consumer device bootstrap process is used, then a companion device can be bootstrapped, but user intervention is required which is impractical for M2M devices
Solution Approach 1:
The device performs self-bootstrapping by automatically sending a provisioning profile request to the provisioning server and downloading the profile without requiring user intervention. This self-service mechanism enables automated bootstrapping of M2M devices that cannot be manually operated.
Solution Approach 2:
The provisioning server serves as an automated intermediary that receives provisioning requests from devices and automatically provides the necessary profiles, eliminating the need for user-triggered bootstrapping processes required by GSMA consumer device specifications.
3Reliability
If a provisioning profile is imprinted in the eUICC chip, then the device has local storage for bootstrapping, but the cost increases significantly
Solution Approach 1:
Instead of imprinting provisioning profiles directly into each device's eUICC chip during manufacturing, the profile is copied from a central provisioning server to the device's eUICC at runtime. This copying approach eliminates costly per-device profile installation while maintaining the requirement for local storage during operation.
Solution Approach 2:
The provisioning profile is prepared and stored in advance on the provisioning server, allowing multiple devices to obtain copies without requiring physical imprinting during manufacturing. This preliminary preparation reduces manufacturing costs while ensuring reliable local storage capability.
Data Source
Figure 1
Figure 2
Figure 2
AI summary
A method (10) for automatic bootstrapping of a device (31,..., 3N) is disclosed. The method (10) is performed by a provisioning node (4) connected to a subscription manager (2). The method (10) comprises receiving (12) a provisioning profile request from the device (31,..., 3N), the provisioning profile request comprising an identifier of the device (31,..., 3N), authenticating (13) the device (31,..., 3N), obtaining (14), based on the identifier of the device (31,..., 3N), a provisioning profile for the device (31,..., 3N), and sending (15) the provisioning profile to the device (31,..., 3N).