eSIM Orchestration refers to the systems, processes, and control logic that manage the full lifecycle of eSIM profile provisioning across Consumer and IoT devices. This includes activation, download, installation, switching, troubleshooting, and automation for both SGP.22 and SGP.32 environments. 

It acts as the operational control plane coordinating devices, RSP servers, connectivity providers, and operator systems. 

Legacy M2M (SGP.02) environments may continue to rely on SM-SR entities; orchestration must account for mixed deployments during migration. 

eSIM Orchestration ensures that:

• eSIM profiles are activated correctly
• Device requests are routed to the right systems
• Lifecycle events execute in the correct sequence
• Connectivity remains consistent and reliable
• Profile switching and fallback rules operate as intended
• Support teams can diagnose issues efficiently

It brings order and transparency to an ecosystem involving: 

• Devices 
• SM-DP+ / SM-DS 
• Connectivity providers 
• Entitlement servers 
• Multi-IMSI systems 
• IoT agents (IPAe/IPAd) 
• Operator back-end systems 

Activation and provisioning touch multiple components: 

• Device hardware and firmware 
• Mobile networks 
• RSP infrastructure 
• Entitlement services 
• Subscription systems 
• OEM-specific activation flows 

Orchestration unifies these elements to: 

• Streamline activations 
• Reduce errors 
• Improve customer experience 
• Support large-scale deployments 
• Automate profile and IMSI management 
• Provide visibility and control 

• Consumer eSIM activation (SGP.22) 
• IoT eSIM automation (SGP.32) 
• Multi-IMSI switching for roaming & fallback 
• Lifecycle actions (download, enable, disable, delete) 
• Fleet-level control 
• Troubleshooting & diagnostics 
• Bulk operations 
• API-driven integrations 

eSIM Orchestration is positioned between the device layer, the connectivity layer, and the RSP infrastructure. 

Consumer: 

• Smartphones 
• Tablets 
• Wearables 
• Laptops 

IoT: 

• Routers / CPE 
• Smart meters 
• POS terminals 
• Telematics units 
• Trackers 
• Industrial equipment 

Supported device-side components: 

• LPA for SGP.22 
• IPAe / IPAd for SGP.32 
• Multi-IMSI applets 

Orchestration interacts with: 

• SM-DP+ (profile storage & delivery) 
• SM-DS (discovery) 
• eUICC interfaces 

It manages all profile lifecycle transitions. 

Includes: 

• Operator networks 
• Roaming partners 
• Radio layers (2G/3G/4G/5G/NB-IoT/LTE-M) 
• APN configurations 
• IMS for VoLTE & VoWiFi 

Orchestration tracks and analyzes connectivity behavior. 

Executes: 

• IoT-based automated provisioning 
• Multi-IMSI rules 
• Region-based profile switching 
• Fallback conditions 
• SLA/QoS-based decisions 

Connects with: 

• Operator CRM 
• Billing and provisioning systems 
• Entitlement servers 
• IoT/Fleet platforms 
• Customer support systems 
• Connectivity management platforms

A unified interface typically used by: 

• Support teams 
• Device provisioning teams 
• Network operations 
• Enterprise customers 

Tracks: 

• QR code and activation code creation 
• SM-DS routing 
• Device LPA requests 
• SM-DP+ download status 
• Profile installation 
• Enablement 
• First attach events 

Supports: 

• QR-based activation 
• In-app activation 
• SM-DS triggered activation 

Handles: 

• Bootstrap → operational profile flows 
• Device agent interactions (IPAe/IPAd) 
• Fallback switching 
• Profile installation and activation 
• Large-scale provisioning 

Use cases: 

• Smart meters 
• CPE & routers 
• Telematics 
• POS 
• Asset trackers 

Orchestration supports: 

• IMSI switching commands 
• Preferred operator logic 
• Regional restrictions 
• SLA/QoS-based switching 
• Roaming fallback rules 

Used for: 

• Travel eSIM 
• Roaming optimization 
• Resilient global IoT deployments 

Across bootstrap, operational, and Fallback profiles (backup subscription): 

• Download 
• Install 
• Enable 
• Disable 
• Delete 
• Reset states 
• Re-provision 

Provides: 

• Activation traces 
• SM-DP+ logs & error codes 
• LPA error codes (consumer) 
• IPAe/IPAd logs (IoT) 
• Network attach logs 
• APN/authentication errors 
• Device-level insights 

Enables mass-scale actions: 

• Bulk activation 
• Bulk profile downloads 
• Bulk lifecycle actions 
• Multi-IMSI updates 
• Fallback switching 
• Device migrations 

Essential for: 

• Enterprise projects 
• MNO migrations 
• Service provider rollouts 
• Fleet operations 

This section describes expected functionality in a typical eSIM orchestration portal (generic, not linked to any vendor). 

Shows: 

• Activation rates 
• Profile success/failure distribution 
• Device distribution (Consumer + IoT) 
• IMSI usage 
• Error heatmaps 
• Operator performance metrics 

Shows: 

• EID / ICCID / IMSI 
• Device model & OS 
• Profile list 
• Current lifecycle state 
• Error logs 
• Installation history 

Displays: 

1. Activation code created 
2. SM-DS registration 
3. Device request
4. SM-DP+ session 
5. Download 
6. Installation 
7. Enablement 
8. Attach 

Shows timestamps and status for each step. 

Allows users to: 

• Trigger download 
• Enable/disable 
• Delete 
• Reset state 
• Switch profiles (IoT) 
• Switch IMSI (multi-IMSI) 

Supports: 

• CSV upload 
• Batch operations 
• Mass reassignments 
• Bulk profile enable/disable 
• Bulk fallback switching 

• OAuth 2.0 
• API keys 
• mTLS (in some implementations) 

Activation APIs 

• Generate activation codes 
• Query activation state 
• Trigger profile download 

Profile APIs 

• List profiles 
• Enable/disable 
• Delete 
• Reassign 

Device APIs 

• Retrieve device metadata 
• Get logs 
• Query IMSI list 
• Trigger IMSI switch 

Event APIs 

• Retrieve activation events 
• Retrieve lifecycle events 

• Download complete 
• Download failed 
• IMSI switch complete 
• Fallback triggered 

• User activation 
• Activation troubleshooting 
• Device upgrades 
• Profile re-download 

• Bootstrap installation 
• Operational provisioning 
• Agent communication 
• Fallback triggers 
• Fleet-wide switching 

• IMSI selection 
• Network steering 
• Roaming fallback 
• Region-based rules 

SGP.22 Common Issues 

• Invalid QR 
• Unreachable SM-DP+ 
• LPA errors 
• Entitlement failures 

SGP.32 Common Issues 

• Bootstrap unreachable 
• IPAe/IPAd timeouts 
• Fallback loops 
• Firmware misconfiguration 

Multi-IMSI Issues 

• Steering not applied 
• Forbidden network 
• IMSI mismatch 

Keep automation simple 

Overly complex rules cause unpredictable behavior. 

Validate subscription provisioning 

CRM or HLR mismatches are the #1 cause of failures. 

Consider QoS metrics 

Best operator ≠ best signal; performance matters. 

Test device firmware 

Especially important in SGP.32 IoT environments.