As 5G fixed wireless access deployments scale globally, a seemingly simple component — the SIM — is undergoing a transformation that has far-reaching implications for CPE procurement, logistics, and operational efficiency. The embedded SIM (eSIM) and its multi-IMSI architecture, governed by GSMA’s SGP.22 and SGP.32 specifications, enable operators to provision, swap, and manage operator profiles on CPE devices without physical SIM card handling. For ISPs, MVNOs, and enterprise operators managing fleets of thousands of distributed CPE units, eSIM technology is not a convenience feature — it is a strategic procurement requirement that directly impacts total cost of ownership, supply chain agility, and subscriber churn.
This technical buyer’s guide examines the eSIM and multi-IMSI architecture as it applies to 5G CPE, covering the GSMA compliance framework, hardware integration considerations, remote SIM provisioning workflows, and practical vendor evaluation criteria for procurement teams specifying next-generation FWA devices.
eSIM Architecture Fundamentals: eUICC, Profiles, and the LPA
At the hardware level, an eSIM implementation in a 5G CPE device consists of an embedded UICC (eUICC) — a soldered, tamper-resistant secure element that conforms to the GSMA SGP.02 (M2M) or SGP.22 (consumer) architecture. Unlike a traditional removable SIM card, the eUICC supports multiple operator profiles stored simultaneously, with secure over-the-air (OTA) profile download, activation, and deletion managed through a Local Profile Assistant (LPA) component integrated into the CPE’s baseband or application processor.
The key architectural choice for CPE procurement teams is between the M2M eUICC architecture (GSMA SGP.02) and the consumer eUICC architecture (GSMA SGP.22):
M2M eUICC (SGP.02). Designed for device-to-device and IoT use cases, the M2M architecture uses a “push” model where the operator’s Subscription Manager-Data Preparation (SM-DP) server pushes profiles to the eUICC through a Subscription Manager-Secure Routing (SM-SR) intermediary. This architecture is well-suited to fixed-location CPE with predictable network attachment patterns, but it requires operator-side SM-SR infrastructure that not all MVNOs maintain.
Consumer eUICC (SGP.22). The consumer architecture uses a “pull” model where the CPE’s LPA initiates profile download from the SM-DP+ server — the operator-controlled platform that prepares and delivers encrypted profiles. SGP.22 is the dominant architecture for smartphones and is increasingly adopted in FWA CPE because it enables end-user or installer-initiated profile switching, supports QR-code-based activation workflows, and integrates naturally with operator mobile apps and self-service portals.
For most FWA and enterprise CPE deployments, SGP.22 consumer eUICC is the recommended architecture due to broader ecosystem support, simpler operator onboarding, and alignment with GSMA SGP.32 — the emerging IoT eSIM standard that extends consumer architecture capabilities to constrained devices.
Multi-IMSI Architecture: Enabling Operator Flexibility at the CPE Level
While eSIM enables profile portability, multi-IMSI capability enables profile concurrency. A multi-IMSI CPE device stores multiple International Mobile Subscriber Identities — each associated with a distinct operator profile — and can switch between them based on network availability, cost optimization rules, or geographic location without requiring a profile download.
In a 5G CPE context, multi-IMSI architecture serves three primary deployment scenarios:
Multi-Carrier Failover for SLA-Grade Deployments. Enterprise CPE deployed at branch offices, retail locations, or remote industrial sites can maintain active IMSIs from two or more operators. If the primary operator’s network experiences congestion or an outage, the CPE’s connection manager — typically implemented in the modem firmware or an SDK-provided middleware layer — triggers an IMSI switch to the secondary operator within seconds, maintaining session continuity for critical applications.
Cross-Border Roaming Optimization. For logistics, transportation, and maritime CPE deployments that cross national boundaries, multi-IMSI with pre-loaded regional operator profiles eliminates roaming charges by enabling the CPE to attach as a local subscriber in each country. The eUICC’s profile management logic, combined with a steering-of-roaming application, selects the lowest-cost profile for the current geographic region — a capability that can reduce connectivity costs by 40–70% compared to international roaming.
MVNO and Wholesale Operator Multi-Tenancy. MVNOs that resell connectivity from multiple host operators can deploy a single CPE SKU with pre-provisioned MNO profiles, activating the appropriate IMSI at subscriber onboarding based on the subscriber’s service plan and coverage area. This eliminates the logistical complexity of stocking operator-specific CPE variants and enables dynamic MNO switching if the MVNO renegotiates wholesale agreements.
Remote SIM Provisioning Workflow: From Factory to Field Deployment
The GSMA-defined RSP (Remote SIM Provisioning) workflow for consumer eUICC CPE follows a four-phase lifecycle:
Phase 1: Factory Provisioning. During CPE manufacturing, the eUICC is loaded with a provisioning profile — a bootstrap connectivity profile that enables the device to attach to a cellular network for the sole purpose of downloading its operational profile. The eUICC’s EID (eUICC ID) is registered with the SM-DP+ server that will manage the device’s profile lifecycle.
Phase 2: Subscriber Onboarding. When a subscriber activates the CPE, the operator provides an activation code — typically delivered as a QR code, a deep link in an operator app, or an SM-DP+ address string in the device’s zero-touch provisioning payload. The CPE’s LPA uses this activation code to establish a secure TLS session with the SM-DP+ server, authenticate via the eUICC’s certificate chain, and download the encrypted operational profile.
Phase 3: Operational Profile Activation. The downloaded profile is installed into an available profile slot on the eUICC, the CPE detaches from the provisioning network, and re-attaches using the operational IMSI. From this point forward, the CPE operates as a standard subscriber device on the selected MNO network.
Phase 4: Lifecycle Management. The operator can remotely enable, disable, or delete profiles through SM-DP+ commands. Profile switching between multiple downloaded profiles (e.g., primary to backup MNO) is managed locally by the LPA based on policy rules configured by the operator or enterprise administrator. The GSMA SGP.32 specification, currently in advanced draft, extends this lifecycle model with bulk profile management capabilities tailored to IoT and CPE fleets.
Hardware Integration Considerations for CPE OEMs and ODMs
For procurement teams evaluating CPE with eSIM capability, the following hardware integration factors should be verified against deployment requirements:
eUICC Chip Selection. The two dominant eUICC secure element vendors — Thales (formerly Gemalto) and G+D (Giesecke+Devrient) — supply GSMA SAS-certified eUICCs with support for both SGP.02 and SGP.22 architectures. STMicroelectronics and Infineon also offer eUICC silicon for cost-optimized IoT and CPE applications. Buyers should verify that the selected eUICC supports the number of concurrent profiles required for the deployment scenario — typically 2–5 profiles for multi-IMSI CPE — and that profile switching latency (measured from IMSI detach to re-attach) meets the service-level requirements for failover applications.
LPA Integration Model. The LPA can be implemented in the modem baseband processor (modem-resident LPA), in the CPE’s application processor (AP-resident LPA), or as a hybrid implementation. Modem-resident LPAs (e.g., Qualcomm’s eSIM framework on Snapdragon X-series modems, MediaTek’s eSIM stack on T-series modems) offer tighter integration with radio state management and lower profile-switching latency. AP-resident LPAs offer greater flexibility for custom operator management UIs and integration with TR-069/TR-369 ACS platforms for remote profile lifecycle management.
Antenna and RF Path Considerations. The provisioning profile bootstrapping phase requires the CPE to achieve network attachment using only the eUICC’s default provisioning IMSI — typically associated with a partner MNO or a global connectivity provider. CPE procurement teams should confirm that the device’s antenna configuration and supported bands cover the provisioning partner’s spectrum in all target deployment geographies, and that the provisioning data path (typically limited to a few megabytes for profile download) does not exhaust a metered bootstrap data allowance.
GSMA Compliance and Security Certification
Any CPE claiming eSIM support should hold GSMA SAS (Security Accreditation Scheme) certification for both the eUICC silicon (SAS-UP) and the SM-DP+ platform (SAS-SM). Additionally, the CPE’s LPA implementation should comply with GSMA SGP.22 v2.4 or later, which includes mandatory support for TLS 1.2 profile delivery encryption and the profile interoperability testing framework defined in GSMA TS.48.
Buyers should request SAS certification documentation from CPE vendors and verify that the eUICC vendor’s SM-DP+ integration has been validated against the operator’s profile delivery infrastructure. In multi-operator deployments, the CPE’s eUICC must support profile policy rules (PPR) as defined in SGP.22 section 3.1.3, enabling the primary operator to control which secondary profiles can coexist on the device.
eSIM vs. iSIM: The Next Integration Step
Looking beyond eSIM, the integrated SIM (iSIM) — where the UICC functionality is embedded directly into the modem’s system-on-chip (SoC) silicon, eliminating the discrete eUICC component — is beginning to appear in cost-optimized CPE designs. Qualcomm’s Snapdragon X80 modem-RF platform and Sony Semiconductor’s Altair ALT1350 chipset both support iSIM architectures compliant with GSMA SGP.31/32 specifications.
iSIM reduces BOM cost (approximately $0.40–0.80 per unit versus discrete eUICC), decreases PCB footprint, and lowers power consumption — advantages that become significant in high-volume CPE deployments. However, the iSIM ecosystem is less mature than eSIM, and operator certification timelines for iSIM-based CPE can extend 3–6 months longer than equivalent eSIM designs. For procurement decisions in 2026, eSIM remains the recommended architecture for mainstream FWA CPE, with iSIM as a forward-looking option for cost-optimized SKUs targeting 2027-2028 volume deployments.
Vendor Selection Criteria: What to Ask CPE Suppliers
When evaluating 5G CPE with eSIM and multi-IMSI capability, procurement teams should include the following requirements in RFQ documentation:
- GSMA SAS certification status for the eUICC component and the SM-DP+ integration path.
- Supported number of concurrent eSIM profiles and measured profile switching latency (detach-to-attach time) under representative network conditions.
- LPA integration model (modem-resident, AP-resident, or hybrid) and compatibility with standard ACS platforms (TR-069/TR-369) for remote lifecycle management.
- Multi-IMSI failover behavior — including automatic vs. policy-driven IMSI switching, and support for steering-of-roaming applications — with documented performance under network degradation scenarios.
- Provisioning profile coverage in target deployment geographies, including bootstrap data allowance sufficient for operational profile download.
- SM-DP+ platform compatibility with the buyer’s existing or planned operator partners, including multi-tenant SM-DP+ support for MVNO and wholesale deployments.
- Firmware OTA (FOTA) update capability for the eSIM LPA stack, ensuring future GSMA specification updates can be deployed without field returns.
For operators building large-scale FWA deployments — particularly those spanning multiple countries or serving enterprise SLA-grade subscribers — eSIM and multi-IMSI capability in CPE is not an optional feature. It is a foundational requirement that determines the speed of subscriber onboarding, the cost of ongoing profile management, and the ability to deliver carrier-grade reliability through multi-operator redundancy. By incorporating these technical evaluation criteria into the CPE procurement process, operators can future-proof their device fleet against profile management complexity and position their FWA services for sustainable growth through 2027 and beyond.