Bootstrap Connectivity — Initial Network Access for SGP.32 IoT Deployments
Overview
ISIMConnect’s Bootstrap Connectivity is a provisional network profile pre-installed on SGP.32-capable SIMs and eSIMs, giving devices initial cellular connectivity the moment they power on — before their permanent operator profile has been provisioned. It is a required element of any SGP.32 remote provisioning deployment: without a bootstrap profile, a device with a blank eUICC has no way to connect to the network, reach the eIM server, and receive its permanent profile. ISIMConnect provides bootstrap connectivity as an integrated part of its SGP.32 SIM and eSIM product stack.
Why Bootstrap Connectivity Is Required for SGP.32
The SGP.32 provisioning sequence creates a circular dependency that bootstrap resolves:
To receive a permanent operator profile, the device must connect to the ISIMConnect eIM server
To connect to the eIM server, the device needs network access
To have network access, the device needs an operator profile
A blank eUICC has no profile. It cannot connect to any network. It cannot reach the eIM. It cannot receive a profile. The provisioning sequence can never start.
Bootstrap connectivity breaks this deadlock: it is a lightweight, provisional profile pre-installed on the eUICC at manufacture, providing just enough network access for the device to find and connect to the eIM and initiate its permanent profile download. Once the permanent profile is downloaded and activated, the bootstrap profile is disabled or deleted — it has served its purpose.
How Bootstrap Connectivity Works in a SGP.32 Deployment
At manufacture: The bootstrap profile is personalised onto the eUICC alongside the device’s SGP.32 SIM or eSIM, during SIM personalisation at ISIMConnect’s SAS-accredited facility.
First power-on: The device powers on in the field. The eUICC activates the bootstrap profile and the device connects to the network using bootstrap credentials.
eIM contact: Using the bootstrap connection, the device’s IPA (IoT Profile Assistant) contacts the ISIMConnect eIM server and registers the device.
Permanent profile download: The eIM instructs the SM-DP+ to deliver the designated permanent operator profile. The profile is downloaded over the air and installed on the eUICC.
Bootstrap deactivation: Once the permanent profile is activated and the device is live on its designated operator network, the bootstrap profile is disabled. The device now operates entirely on its permanent profile.
What Network Does the Bootstrap Profile Use?
The bootstrap profile typically uses a roaming or neutral network arrangement specifically for the purpose of reaching the eIM — it is not intended for data traffic or long-term connectivity. Its sole function is providing the minimum network access needed to initiate the first eIM contact and permanent profile download.
ISIMConnect provisions bootstrap connectivity as part of its SGP.32 SIM personalisation process — you do not need to source or arrange bootstrap access separately. It is included as a component of the SGP.32 SIM and eSIM product.
Is Bootstrap Connectivity Needed for All ISIMConnect SIM Products?
No — bootstrap connectivity is only required for SGP.32 remote provisioning deployments.
SGP.32 Plastic SIM – Yes — device needs bootstrap to reach eIM for first profile download
SGP.32 eSIM – Yes — same requirement
Multi-IMSI Plastic SIM – No — profiles are pre-loaded at manufacture, no eIM contact needed
Multi-IMSI eSIM – No — same as Multi-IMSI Plastic SIM
OTA Single MNO SIM – No — device activates directly on the pre-loaded single operator profile
SIM Chip – No — single operator profile loaded at manufacture
Frequently Asked Questions
Q: What is bootstrap connectivity for eSIM?
A: Bootstrap connectivity is a provisional network profile pre-installed on an eSIM (eUICC) at manufacture, giving IoT devices initial cellular access on first power-on before their permanent operator profile is downloaded. It provides just enough connectivity for the device to reach the eIM server and initiate its permanent profile download via GSMA SGP.32 remote provisioning.
Q: Why does a SGP.32 device need a bootstrap profile?
A: Without a bootstrap profile, a device with a blank eUICC has no network access and cannot reach the eIM server to download its permanent operator profile. Bootstrap breaks this deadlock by providing provisional connectivity that enables the first eIM contact — after which the permanent profile takes over and the bootstrap profile is disabled.
Q: Does ISIMConnect provide bootstrap connectivity separately, or is it included?
A: Bootstrap connectivity is included as an integrated part of ISIMConnect’s SGP.32 SIM and eSIM products. It is pre-installed during SIM personalisation at SAS-accredited facilities — you do not need to source or configure bootstrap access separately.
Q: Does the bootstrap profile remain active after the permanent profile is downloaded?
A: No. Once the permanent operator profile is downloaded, installed, and activated via the eIM, the bootstrap profile is disabled. The device then operates entirely on its permanent operator profile for the remainder of its deployed life.
Q: Is bootstrap connectivity required for Multi-IMSI SIM?
A: No. Multi-IMSI SIM profiles are pre-loaded at manufacture and the device switches between them automatically on-device. There is no eIM contact required, and therefore no need for bootstrap connectivity.
Q: What network does the bootstrap profile use?
A: The bootstrap profile uses a provisional neutral network arrangement specifically for reaching the eIM — not a full commercial operator plan. Its sole purpose is enabling the first eIM connection. Full M2M data connectivity is delivered by the permanent operator profile downloaded through the eIM.