# SM-DS — Subscription Manager Discovery Service

> SM-DS (Subscription Manager — Discovery Service) is the GSMA-defined directory that lets an eUICC discover that one or more SM-DP+ servers have profile downloads waiting for it, without the user needing to scan a QR code or type an activation code. It is the silent partner of SM-DP+: SM-DP+ holds the profile, SM-DS tells the eUICC where to fetch it.

- Canonical URL: https://www.broadnet.me/answers/sm-ds
- Language: en
- Last reviewed: 2026-05-28
- Publisher: BroadNet (https://www.broadnet.me)

## What it actually does

When a device boots or polls (typically on first power-on or after a profile-change event), its Local Profile Assistant (LPA) queries the GSMA root SM-DS, which returns the address of any operator SM-DP+ that has a pending profile for that EID. The LPA then contacts the operator SM-DP+ and runs the standard SGP.22 ES9+ profile download. SM-DS does not handle profile data; it is purely a pointer registry. This is the mechanism behind the iOS "eSIM Quick Transfer" and Android "automatic eSIM activation" experiences.

## Why it matters commercially

SM-DS removes the activation-code distribution problem. Without it, every eSIM customer needs a unique QR code or 16-digit activation code emailed/printed/displayed to them — friction that kills conversion in IoT and consumer-onboarding flows. With SM-DS, the operator pushes the profile reference, the device discovers it, and activation completes without user input. For MVNOs and travel-eSIM brands, this is the difference between a 60% and a 95% activation rate.

## Latency, scale, and compliance angle

SM-DS responses are typically under 1 second end-to-end. The GSMA Root SM-DS is operated under SAS-SM accreditation; alternate SM-DS instances (operator-hosted or vendor-hosted) federate through the root. BroadNet's eSIM VSM platform supports both root-SM-DS discovery and operator-private alternate SM-DS hosting for B2B IoT deployments that need a closed discovery loop. See /operators/esim-vsm for the architecture diagram.

## Privacy and compliance considerations

SM-DS sees the EID and the SM-DP+ address but never sees profile data. It logs discovery events — which can in aggregate reveal device-activation patterns — and is therefore in scope for SAS-SM audit on access controls, key custody, and log retention. For privacy-sensitive deployments, a tenant-private SM-DS keeps discovery events out of the global federation.

## Related

- [All answers](https://www.broadnet.me/answers)
- [Glossary](https://www.broadnet.me/answers)
- [SM-DP+ — Subscription Manager Data Preparation, explained](https://www.broadnet.me/answers/sm-dp-plus)
- [eUICC — the embedded UICC chip explained](https://www.broadnet.me/answers/what-is-euicc)
- [EID — the eUICC identifier, explained](https://www.broadnet.me/answers/what-is-eid)
- [eSIM ES interfaces — ES2+, ES8+, ES9+, ES10 explained](https://www.broadnet.me/answers/esim-es-interfaces-explained)
- [SGP.32 — eSIM IoT for M2M without the SM-DP+ dance](https://www.broadnet.me/answers/sgp-32-esim)
- [eSIM VSM platform](https://www.broadnet.me/operators/esim-vsm)