eSIM lawful interception presents unique technical challenges compared to traditional SIM-based interception. The transition from physical SIM cards to embedded SIM (eSIM) technology is reshaping the mobile telecommunications landscape. Driven by the GSMA’s Remote SIM Provisioning (RSP) architecture, eSIM enables subscribers to switch operators, activate profiles, and manage multiple subscriptions without physically replacing a SIM card. For consumers, this means greater flexibility and convenience. For operators — and particularly for those responsible for lawful interception compliance — eSIM introduces new complexities that must be understood and addressed.
This article examines how the RSP architecture affects lawful interception, identifies the specific challenges that eSIM creates for target identification and interception management, and provides practical guidance for operators seeking to maintain compliance in an eSIM-enabled environment.
How eSIM Lawful Interception Works
The GSMA RSP architecture defines the ecosystem for managing eSIM profiles. The key components include the Subscription Manager — Data Preparation (SM-DP+), which prepares and securely delivers operator profiles to eSIM devices; the Subscription Manager — Discovery Server (SM-DS), which facilitates the discovery of available profiles; the eUICC (embedded Universal Integrated Circuit Card), which is the secure element within the device that hosts one or more operator profiles; and the Local Profile Assistant (LPA), which is the software on the device that manages profile download, installation, and switching. For IoT devices, GSMA SGP.31/SGP.32 replaces the user-driven LPA with a remote eSIM IoT Manager (eIM).
Under the RSP model, an operator’s profile — containing the IMSI, authentication credentials, network access configuration, and other parameters — is downloaded and installed onto the eUICC remotely. Multiple profiles can coexist on a single eUICC. Older eUICCs allow only one enabled profile at a time; since GSMA SGP.22 v3, devices supporting Multiple Enabled Profiles (MEP) can run two at once. Subscribers can switch between profiles — and effectively between operators — through a software operation on the device, without any physical intervention.
This dynamic, software-driven provisioning model is fundamentally different from the traditional physical SIM model, where the IMSI is personalised onto a card that has to be physically delivered. The implications for lawful interception are significant.
Target Identification Challenges
Lawful interception orders typically identify the target by one or more identifiers: MSISDN (phone number), IMSI (subscriber identity), IMEI (device identity), or IP address. The eSIM model complicates each of these identification methods in different ways.
MSISDN-based targeting is affected by the ease with which subscribers can change operators — and by extension change their MSISDN — through a simple profile switch. A target who suspects surveillance may switch to a different profile and MSISDN without a physical SIM changing hands. Similar switches have always been possible with dual-SIM phones. Each new profile still means a new subscription (in Germany, prepaid profiles require an identity check before activation, § 172(2) TKG), and its download is logged against the device’s EID. The operator that was performing the interception may lose visibility of the target entirely if the target activates a profile from a different operator.
IMSI-based targeting faces similar challenges. Each operator profile on the eUICC has its own IMSI. When the target switches profiles, a different IMSI becomes active, and the original IMSI is no longer visible on the network. The operator intercepting based on the original IMSI will see the target apparently disappear from the network.
IMEI-based targeting is more stable in the eSIM context, as the IMEI is associated with the device rather than the SIM profile. Note that dual-SIM and multi-profile devices carry a separate IMEI for each simultaneously active subscription, and that the network usually learns the IMEI only at registration. However, IMEI-based interception has its own limitations — it may capture communications from other users who share the device, and it does not help if the target uses multiple devices.
IP address-based targeting is inherently dynamic and is not specifically affected by eSIM, but the overall complexity of targeting in an eSIM environment may lead law enforcement to rely more heavily on IP-based identification, with its own challenges of dynamic allocation and network address translation.
Profile Switching and Interception Continuity
One of the most significant challenges that eSIM creates for lawful interception is the potential for interception discontinuity during profile switches. When a target switches from one operator profile to another on the same device, the interception that was active on the first operator’s network must be coordinated with a new interception on the second operator’s network. In practice, law enforcement must identify the new operator, obtain a new order and serve it there, which may take hours or days, during which the target’s communications go unmonitored.
The speed and ease of profile switching in the eSIM model — which can be accomplished in seconds on many devices — contrasts sharply with the time required to establish a new interception on a different operator’s network. This temporal gap is an investigative challenge for law enforcement rather than a compliance gap for the original operator, whose obligation ends at its own subscription and the identifiers named in the order.
Addressing this challenge requires enhanced coordination mechanisms between operators and law enforcement, potentially including automated notifications when a target’s profile is deactivated and standardised procedures for rapidly establishing interceptions on the target’s new operator. Standardised solutions are not yet widely available.
Multi-Profile and Multi-Device Scenarios
eSIM technology enables scenarios that are difficult to address with traditional interception approaches. A single device may host multiple operator profiles, potentially from operators in different countries. A single subscriber may have eSIM profiles on multiple devices — a smartphone, a tablet, a smartwatch, and a laptop. Each combination of profile and device creates a potential communication channel that may need to be intercepted.
For operators, this means that the scope of an interception may extend beyond the traditional single-subscriber, single-device model. Within its own customer base, the operator should be able to tell law enforcement which other subscriptions or eSIM profiles the same customer holds, so that the order can be extended. It can intercept only the identifiers the order names.
For law enforcement, the multi-profile model means that a single interception order may not be sufficient. If the target has profiles on multiple operators’ networks, separate orders may need to be issued to each operator. The coordination of these multiple orders — ensuring complete coverage without gaps — adds complexity to the investigative process.
Implications for the LI System
To maintain effective lawful interception in an eSIM environment, operators must ensure that their LI systems address several specific requirements. First, operators should understand what the network actually sees. Switching profiles happens locally on the device. The operator’s network sees it the way it sees a phone being switched off: the target’s subscription deregisters, and the existing interception reports this as IRI. The SM-DP+ is not a real-time LI source. Its value is in the records it keeps, such as which EID a profile was downloaded to, which can support disclosure requests. The LI system should not push target data to the SM-DP+, which is often operated by a third party.
Second, the LI system must support the correlation of multiple identifiers associated with the same subscriber. A target may be known by different MSISDNs, IMSIs, and IP addresses depending on which profile is active. The LI system must maintain a mapping between these identifiers and the target’s interception order, ensuring that every identifier named in the order (MSISDN, IMSI/SUPI, IMEI/PEI) is intercepted, and that law enforcement can quickly learn which further identifiers the same customer uses.
Third, the LI system should deliver the standard registration and deregistration events promptly, since a profile switch shows up on the network as the target’s subscription deregistering. This information can be valuable to law enforcement in understanding the target’s behavior and in deciding on follow-up orders.
Fourth, the operator’s warrant management system must be capable of handling the additional complexity introduced by eSIM. This includes the ability to modify interception parameters when the order is amended, to report promptly when a target’s subscription goes inactive, so that law enforcement can decide on follow-up orders, and to keep a complete audit trail of every order amendment, identifier change and task activation or deactivation.
Regulatory and Standards Developments
LI standards address the issue indirectly: identifiers are always tied to the subscription or device, not to the SIM form factor. 3GPP’s 5G LI architecture (TS 33.127/33.128) is SIM-agnostic: it intercepts by SUPI, PEI and GPSI, whether the credentials sit on a physical SIM or an eSIM profile.
National LI rules generally do not treat eSIM separately. In Germany, the TKÜV and TR TKÜV are technology-neutral: interception is tied to identifiers such as MSISDN, IMSI/SUPI and IMEI/PEI, so it applies to eSIM subscriptions exactly as to physical SIMs.
Conclusion
eSIM technology and the RSP architecture introduce significant new challenges for lawful interception, primarily related to target identification, interception continuity, and multi-profile scenarios. These challenges are not insurmountable, but they require operators to report registration events promptly, keep reliable records linking EID, ICCID and IMSI, and answer subscriber-data requests quickly. eSIM does not change an operator’s LI obligations; it changes how quickly law enforcement needs to learn about a target’s other subscriptions.
Practical Steps for Operators
Operators should begin by assessing their current eSIM deployment and its impact on their existing LI capabilities. This assessment should identify any gaps in target identification, interception continuity, or multi-profile handling. Based on the assessment, operators should develop a roadmap for enhancing their LI systems to address eSIM-specific challenges, prioritising the highest-risk gaps first. Prompt delivery of registration and deregistration events, and the ability to answer subscriber-data requests from the operator’s own EID, ICCID and IMSI records, are the foundation for supporting law enforcement in an eSIM environment. Operators should also engage with their national regulatory authority to understand any specific guidance or requirements related to eSIM and LI compliance, and should participate in industry forums and standards development activities to help shape the emerging solutions.
As eSIM adoption accelerates, eSIM lawful interception challenges will become more pressing. Operators should proactively address eSIM lawful interception requirements in their compliance roadmaps.
Related Articles
For further reading on related topics, explore these articles:
- LI for eSIM-Only MVNOs: Unique Challenges and Practical Solutions
- MVNO vs MNO: Who Is Legally Responsible for Lawful Interception?
- Network Slicing in 5G SA: How It Complicates (and Can Simplify) LI Targeting
External Resources
The following external resources provide additional context and official documentation:
