eSIM has evolved from a connectivity feature into a foundational technology for next-generation devices. OEMs must understand eSIM because it impacts: 

• Device hardware design 
• Firmware architecture 
• Security compliance
• Regulatory approval 
• Integration with operators and RSP providers 
• Global logistics and lifecycle management 

A robust eSIM strategy improves: 

• Time-to-market 
• Interoperability 
• Connectivity resilience 
• Global deployment capabilities 
• Device cost optimization (no removable SIM slot) 

An embedded Universal Integrated Circuit Card (eUICC) is a secure element that contains: 

• eSIM Operating System (OS) 
• Profile storage (multiple profiles) 
• Security domains 
• File system 
• Cryptographic keys 
• Applets (including IPAe for IoT) 

It enables remote management of operator profiles throughout the device’s lifecycle. 

An eUICC can store: 

• Bootstrap profile 
• Operational profiles 
• Fallback profiles (backup subscription) 
• Regional/local profiles (regulatory) 

Profile lifecycle management depends on the chosen RSP standard (SGP.22 or SGP.32). 

OEMs must choose the appropriate packaging based on device category, durability requirements, and manufacturing constraints. 

• Standard industrial embedded SIM package 
• Widely used across IoT and consumer devices 
• Soldered onto PCB 
• Good durability for temperature, vibration, humidity 

• Ultra-small footprint 
• Ideal for:
  Miniaturized devices
  Wearables
  Sensors
  Devices requiring strict board space optimization 

• More sensitive to manufacturing processes 
• Requires tighter reflow specifications 
• Many WLCSP implementations require underfill for mechanical stability and thermal performance. 

• Still used in development boards or hybrid architectures 
• Not recommended for long-term industrial deployments 

eSIM packages must be selected for: 

• Operating temperature range 
• Shock and vibration resistance 
• Moisture and corrosion exposure 
• Solder reflow compatibility 
• Encapsulation materials 

Many IoT deployments (smart meters, agriculture, transportation) require robust, industrial-grade eSIMs.

The eSIM OS is a secure operating system implementing: 

• GlobalPlatform Card Specifications 
• GSMA eSIM specifications (SGP.22 / SGP.32) 
• JavaCard or proprietary applet frameworks 
• Secure domains and key management 

Core components: 

1. File System

• Stores profiles 
• Stores security parameters 
• Stores profile metadata 

2. Security Domains

• ISD-P (Issuer Security Domain – Profile) 
• ISD-R (Root domain) 
• Applet domains 

3. eSIMApplets 

These support: 

• Support for RSP commands 
• Network authentication 
• Multi-IMSI logic (if needed) 
• IoT assistants (IPAe) 

4. Cryptographic Engine

Handles: 

• Authentication 
• Secure channel establishment 
• Profile encryption 
• Key rotation 
• Certificates 

OEMs must ensure compatibility with the modem’s CAT-M/NB-IoT/4G/5G layer and the profile type. 

SGP.32 introduces two possible IoT Profile Assistants. OEMs must choose the model aligned with their device architecture. 

IPAe is part of the eUICC firmware. 

Advantages: 

• Minimal integration on device firmware 
• Reduced software maintenance 
• Simplified certification 
• Works well with constrained devices 

Limitations: 

• Less flexibility for advanced logic 
• IPAe communication is anchored to the eUICC and typically relies on the modem’s cellular data channel. In some device architectures, an OEM can implement a relay mechanism that allows IPAe traffic to pass through non-cellular paths, but this requires custom integration 

Ideal for: 

• Smart meters 
• Sensors 
• NB-IoT devices 
• Devices with limited MCU/OS capabilities 

IPAd runs on the device processor (Linux, RTOS, microcontroller). 

Advantages: 

• Can use Wi-Fi/Ethernet for provisioning 
• Provides richer logs and diagnostics 
• More control over orchestration flows 
• Easier to evolve/patch via OTA updates 

Limitations: 

• Requires OEM integration 
• Must pass certification 
• Slightly larger footprint 

Ideal for: 

• CPE, routers, gateways 
• POS terminals 
• High-end telematics devices 

Depending on the assistant (IPAe/IPAd) and download mode, communication may use: 

• Device connects directly to SM-DP+ 
• Uses IP protocols such as HTTPS 
• Suitable for: 
• Devices with stable power 
• CPE, gateways, POS 
• IPAd-based implementations 

• Device communicates with eIM using lightweight protocols 
• eIM orchestrates profile delivery 
• Suitable for:
  Constrained NB-IoT and LTE-M devices
  Battery-powered sensors
  Devices with intermittent connectivity 

OEMs must ensure the device OS and modem support the required protocol stack. 

Manufacturing stage is critical for preparing devices for remote provisioning. 

1. eUICC Initialization

• Loading eUICC OS 
• Injecting certificates 
• Initializing security domains 

2. EID Allocation 

• Each eUICC receives a globally unique EID 

3. Secure Key Injection 

• Cryptographic key material for SM-DP+ pairing 
• GSMA SAS-UP compliance required 

4. Profile Preloading (Optional) 

OEM may preload: 

• Bootstrap profile 
• Local regulatory profiles 
• Temporary test profiles 

5. Connectivity Verification 

Ensure: 

• Device can attach with bootstrap 
• Profile integrity is valid 
• Modem successfully reads eUICC 

6. Factory-Level Testing 

Includes: 

• ICCID integrity 
• EID scanning 
• Profile activation test 
• AT command communication tests 
• SIM/eUICC presence detection 

OEMs must ensure their device is ready to operate under: 

Requires: 

• LPA (Local Profile Assistant) inside OS 
• SM-DP+ & SM-DS interoperability 
• Device UI for activation (QR/app/settings) 
• OEM certificate signing 
• Reliable network stack for HTTPS 

Used in: 

• Smartphones, wearables, consumer tablets 
• Laptops with eSIM 

Requires: 

• IPAe or IPAd integration 
• Support for direct/indirect download 
• Retry and sleep management 
• Alignment with constrained networks (NB-IoT, LTE-M) 
• eIM interoperability testing 

Used in: 

• IoT gateways, industrial meters, sensors 
• POS, trackers, telematics 
• Connected appliances 

Certification is essential for interoperability and security. 

1. GSMA SAS-UP / SAS-SM 

For facilities handling: 

• Key injection 
• Profile creation 
• eUICC manufacturing 

(Not performed by OEMs but relevant for supply chain selection.) 

2. RSP Interoperability Tests 

OEM’s device must pass: 

• SM-DP+ interoperability 
• SM-DS interoperability (Consumer) 
• eIM interoperability (IoT) 
• Profile download, installation, enablement sequences 

3. Modem + eUICC Integration Tests 

Validation across: 

• Modem firmware AT commands 
• SIM presence / voltage switching 
• SIM resets and timing 
• Power cycling behavior 

4. Regional Certifications 

Depending on deployment: 

• CE
• FCC 
• PTCRB 
• GCF 

These must be validated AGAIN after integrating eUICC hardware. 

Common OEM Issues: 

1. eSIM Not Detected 

Possible causes: 

• Improper soldering (MFF2/WLCSP)
• Faulty PCB routing 
• Incorrect power sequencing 

Fix: 

• Validate electrical design 
• Review SIM reset/power timing 

2. EID Duplication 

Possible causes: 

• Factory error in personalization 

Fix: 

• Reject affected units 
• Re-initialize eUICC 

3. Profile Download Failure During Factory Tests 

Possible causes: 

• Firewall blocking SM-DP+ 
• Incorrect APN
• eUICC not initialized 

Fix: 

• Validate eUICC personalization 
• Verify connectivity path 

4. Device Cannot Reach eIM 

Possible causes: 

• Incorrect URL 
• TLS/DTLS handshake failure 
• Wrong protocol stack (e.g., CoAP/MQTT mismatch) 

Fix: 

• Validate certificates 
• Confirm protocol support 

5. IPAe/IPAd State Machine Errors 

Possible causes: 

• Firmware bugs 
• Agent not compliant with SGP.32 sequences 

Fix: 

• Reset profile state 
• Update IPA firmware 
• Validate via test harness 

1. Decide Early BetweenIPAeand IPAd 

Impacts entire firmware and provisioning architecture. 

2. Use Industrial-GradeeUICCPackages for Harsh Environments 

Especially WLCSP and MFF2 variants for rugged deployments. 

3. Choose the Right Bootstrap Strategy

A robust bootstrap profile is critical for: 

• Remote activation 
• Fallback 
• Global roaming resilience 

4. ValidateAcross Multiple MNOs During Development 

Ensures global interoperability. 

5. Ensure AT Command Compatibility

Many issues originate from modem/eUICC communication gaps. AT command implementation varies across modem vendors (Quectel, Telit, Sierra, u-blox), and OEMs must validate full command coverage. 

6. Implement Strong Logging

Device logs are vital for diagnosing provisioning issues. 

7. Test Power Cycling & Sleep-Wake Behavior Thoroughly

Especially for LTE-M / NB-IoT and battery-powered devices.