> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/anynet-sim/esim-and-remote-provisioning/about-euicc-sim-profiles.md).
# About eUICC SIM profiles
An eUICC SIM profile acts as a virtual SIM within the SIM container. Downloading and enabling a new profile means that an IoT device can switch to a different network operator without the need to physically change the SIM.
Eseye provides the [Connectivity Management Platform (CMP)](/anynet-sim/connectivity/about-the-connectivity-management-platform.md) to manage loading, switching, and deleting profiles.
Each profile contains:
* An [ICCID](/glossary/glossary.md) to uniquely identify the profile
* One or more [IMSIs](/glossary/glossary.md), depending on the profile type, to identify the network subscriber
* Operator subscription data, including authentication credentials
* Policy rules
The content and structure of profiles is standardised to ensure interoperability between all network. Each IMSI account is provided by the mobile network to which it connects.
The number of profiles that can be stored on an eUICC is limited only by the memory available and the size of each network operator’s profile. For information about memory capacity, see the relevant [datasheets](/anynet-sim/readme.md#comparing-anynet-sim-specifications).
You can only enable one profile at any time. The profile currently in use (enabled) is called the active profile.
{% hint style="info" %}
For information about how eUICC IMSIs are managed OTA, see [Understanding the GSMA RSP M2M general architecture](/anynet-sim/esim-and-remote-provisioning/understanding-the-gsma-rsp-m2m-general-architecture.md).
For information about eUICC, see [eUICC overview](/anynet-sim/esim-and-remote-provisioning/euicc-overview.md).
{% endhint %}
eUICC SIMs support the following profile types:
Bootstrap profile (also known as the provisioning profile)
eUICC SIMs are pre-configured with a [multi-IMSI bootstrap profile](/anynet-sim/how-anynet-sims-work/understanding-multi-imsi-functionality.md) that has full access to up to ten mobile networks and their corresponding [roaming agreements](/anynet-sim/how-anynet-sims-work/understanding-roaming.md). This enables the device to connect to a network as soon as it starts up. For more information, see [How long does an IMSI rotation or switch take?](/anynet-sim/how-anynet-sims-work/understanding-imsi-rotation-vs-imsi-switching.md#imsi-rotation-and-switching-duration).
The bootstrap profile enables communication with the [Remote SIM Provisioning (RSP)](/anynet-sim/esim-and-remote-provisioning/about-remote-sim-provisioning-rsp.md) system when the device first starts up. With an [eUICC SIM](/anynet-sim/esim-and-remote-provisioning/euicc-overview.md), the device can use the RSP system to download an operational profile over-the-air (OTA) and activate it to connect to a more suitable network.
{% hint style="info" %}
MNOs typically charge for RSP, so Eseye will also charge for OTA functions. These charges are detailed in your contract.
{% endhint %}
For information about how a device uses different IMSIs to connect to a network, see [Understanding the IMSI rotation and switching process](/anynet-sim/how-anynet-sims-work/understanding-the-imsi-rotation-and-switching-process.md).
For a comparison of bootstrap and operational profiles, see [Bootstrap profile vs operational profile comparison](/anynet-sim/esim-and-remote-provisioning/bootstrap-profile-vs-operational-profile-comparison.md).
Operational profile (also known as a step 2 profile)
Operational profiles are single-IMSI profiles with full access to one mobile network and its corresponding [roaming agreements](/anynet-sim/how-anynet-sims-work/understanding-roaming.md).
The [CMP](/anynet-sim/connectivity/about-the-connectivity-management-platform.md) manages loading and deleting operational profiles over-the-air (OTA) in an Eseye-enabled [eUICC SIM](/anynet-sim/esim-and-remote-provisioning/euicc-overview.md). An operational profile is usually downloaded and activated after a device is deployed, to ensure that each device can [localise](/anynet-sim/how-anynet-sims-work/understanding-localisation.md), rather than roaming on a network within the bootstrap profile.
This is useful for ensuring your IoT devices adhere to local legislation and network policies. It is also useful if you manufacture thousands of devices that are shipped globally, and you do not know where each batch will end up.
You can use operational profiles on battery operated devices and mobile devices. For advice, contact Support ().
{% hint style="info" %}
You can flag the bootstrap or an operational profile as the fall-back (see below
{% endhint %}
Test profile
Test profiles are single-IMSI profiles used for device certification, production-line sampling, or product demonstrations.
For more information, see [Eseye test profile](/anynet-sim/esim-and-remote-provisioning/eseye-test-profile.md).
eUICC SIMs can include a [GSMA Generic eUICC test profile](/anynet-sim/esim-and-remote-provisioning/gsma-generic-euicc-test-profile.md).
Customers must use [AT commands](/anynet-sim/esim-and-remote-provisioning/gsma-generic-euicc-test-profile.md#to-switch-to-and-from-the-generic-euicc-test-profile-using-at-commands) to enable or disable the test profile.
## About fall-back and roll-back
As a safeguard against failed connections, eUICC SIMs use fall-back and roll-back.
About fall-back
One profile is designated as the fall-back. If the active (enabled) profile loses connectivity, or is rejected, disabled, or deleted, the device enables the fall-back profile in its place after up to 23 minutes. The timing depends on how the module is manufactured.
Eseye configures the fall-back using the [Connectivity Management Platform (CMP)](/anynet-sim/connectivity/about-the-connectivity-management-platform.md).
{% hint style="info" %}
The fall-back timer is separate from the [multi-IMSI rotation timer](/anynet-sim/how-anynet-sims-work/understanding-imsi-rotation-vs-imsi-switching.md#imsi-rotation-and-switching-duration) and overrides multi-IMSI rotation if no connection occurs for 23 minutes.
You cannot delete the profile assigned as the fall-back.
{% endhint %}
To maximise connectivity when a device first starts, Eseye usually defines a [multi-IMSI bootstrap profile](/anynet-sim/how-anynet-sims-work/understanding-multi-imsi-functionality.md) as the fall-back on an AnyNet+ SIM. This gives the device access to up to ten networks for greater connectivity.
If the fall-back occurs as a result of connectivity failure, the CMP uses its rules-based engine to determine whether and when to attempt to switch the device back to a preferred operational profile.
#### Disabling fall-back
If a device is localised using an operational profile and the connection is stable, the CMP can define an operational profile as the fall-back, which effectively disables fall-back to the bootstrap profile. This prevents the device switching between profiles if it temporarily loses connectivity. For example, a tracking device in a car may lose connectivity if the car is parked underground overnight, but it reconnects on the fall-back profile, in this case a single-IMSI operational profile, the next day when the car leaves the car park.
About roll-back
{% hint style="info" %}
This feature is for newly downloaded profiles only.
{% endhint %}
After connection is established using an eUICC profile, if you load and enable a new profile and the connection fails, then the SIM rolls back to the previously connected profile. This is managed by the Connectivity Management Platform.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.eseye.com/anynet-sim/esim-and-remote-provisioning/about-euicc-sim-profiles.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.