> 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/how-anynet-sims-work/understanding-imsi-rotation-vs-imsi-switching.md).

# Understanding IMSI rotation vs IMSI switching

If your SIMS use multi-IMSI functionality, the device can rotate or switch between IMSIs in order to maximise connectivity.

## About IMSI rotation

If a device modem loses connection or cannot connect to a network, a SIM application rotates the SIM to the next IMSI after three minutes. It presents the alternative IMSI to the modem, which refreshes its settings.

{% hint style="info" %}
IMSI rotation only works with a SIM or eUICC profile that has multi-IMSI functionality.
{% endhint %}

![](https://2995386447-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzlTL8FVu6GaQkB5i1TRY%2Fuploads%2FXpgNZxU8aDW8qTi9mWMH%2FMultiImsi_ImsiRotation.svg?alt=media)

In the following example, the SIM has three IMSIs. When it cannot connect using Operator A, the SIM rotates to IMSI #2 and connects using Operator B:

![](https://2995386447-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzlTL8FVu6GaQkB5i1TRY%2Fuploads%2FIOrGyQi3ZRQtzzqoKlUk%2FMultiImsi_MultiImsiRotation.svg?alt=media)

## About IMSI switching

After connection is established, the Connectivity Management Platform (CMP) can instruct the SIM to switch to a specific IMSI. This is useful for [localising](/anynet-sim/how-anynet-sims-work/understanding-localisation.md) the IoT device to the home network, or [steering](/anynet-sim/how-anynet-sims-work/understanding-roaming.md) the device to a different roaming partner.

In the following example, the SIM first connects using Operator A, but is switched onto IMSI #3, to use Operator C's roaming partner (Operator D), for legislative purposes:

![](https://2995386447-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzlTL8FVu6GaQkB5i1TRY%2Fuploads%2FVYCHcPII24AMe8TLdkYX%2FMultiImsi_MultiImsiSwitching.svg?alt=media)

## IMSI rotation and switching duration

The length of time taken for an IMSI to rotate or switch, either on the device or OTA, depends on the following factors:

* Time set for auto-rotation (usually 3 minutes)
* Device power constraints or optimisations, such as the length of time it is awake
* Modem setup, such as how often and how long it connects to a network
* The number of IMSI accounts available if connectivity is not established. Three IMSIs are quicker to rotate through than ten IMSIs.
* Whether the device is mobile or static. If a device is constantly moving, it may take a while to establish a network connection.

{% hint style="info" %}
You can manage configurations and optimise timing using the Rules Engine
{% endhint %}

## IMSI rotation and switching configuration options

Eseye supports the following:

* Enable or disable the IMSI rotation feature. For [localisation](/anynet-sim/how-anynet-sims-work/understanding-localisation.md) purposes, you may need to disable the IMSI rotate feature to ensure that the device remains on a preferred network.
* Add or remove IMSIs from the SIM. This is important to ensure that the device can connect to available networks at the best rates, or for legislative purposes, throughout its lifetime.
* Eseye can work with the customer to customise the SIM application, either at build time or during the service life of the IoT device where the SIM exists.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eseye.com/anynet-sim/how-anynet-sims-work/understanding-imsi-rotation-vs-imsi-switching.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.