When a subscriber chooses your service, the profile still has to reach their device. As the operator, you need that delivery to follow your provisioning process and give your teams a clear installation result.
OVOO SM-DP+ prepares, protects and delivers eSIM profiles using GSMA SGP.22 v2.5. It connects profile orders from your management backend with HSS subscriber provisioning, so eSIM delivery becomes part of how you bring subscribers onto your network.
For the subscriber, joining your service includes a profile download. Your provisioning team links the profile to the subscription, while operations need to know whether installation succeeded.
After choosing a subscription, the subscriber uses the activation details to add an eSIM on a compatible device. They can receive the profile digitally, without collecting a SIM card or waiting for one to arrive.
SIM delivery becomes part of your digital onboarding.
A new subscriber record in the HSS is the starting point for profile creation. Your management backend places the order, linking eSIM delivery to the provisioning process behind your service.
eSIM fits the provisioning flow your teams already manage.
When a subscriber cannot connect, operations need to know whether the profile was installed. Download records, installation notifications and alarms help the team trace delivery before investigating authentication or access.
Support starts with evidence of what reached the device.
Your management backend controls when a profile is ordered. SM-DP+ then prepares it for the target eUICC and handles the download through the device's Local Profile Assistant (LPA).
Profile preparation + delivery
Here is what happens after your backend places an order, and what the subscriber sees along the way.
Add an eSIM. Use a QR code from your operator to add a mobile plan.
Example eSIM setup. No real profile is downloaded. Drag to rotate the phone. Arrow keys rotate. R, Home or a double click resets the view. Steps advance automatically while the phone is visible. Tap the screen during scanning or processing, use its button, or press Enter to advance. The final screen waits for Done to restart.
Once the eSIM is installed, its credentials can also identify the subscriber on your Hotspot 2.0 network. The Wi-Fi service uses that identity for authentication and access.
SM-DP+ delivers the profile.Your network controls access.
Explore OVOO AAAAAA and HSS authenticate the subscriber through EAP-AKA using the credentials in the installed profile.
The access points carry the PLMN information for your Hotspot 2.0 service.
The Hotspot 2.0 core manages subscriber sessions and passes charging requests through an OCS gateway.
The access points send authentication requests through a RADIUS proxy, using RADIUS over TLS.
Follow a subscriber from eSIM installation through EAP-AKA authentication to Hotspot 2.0 access. The demo shows how OVOO SM-DP+ works with AAA, HSS and charging to deliver the service.
We suggest starting with new subscriptions. If your backend can route a small batch of ES2+ orders to OVOO, you can follow those orders through to installation before switching more traffic. Existing subscribers can keep their installed profiles during that pilot.
Each activation code contains the address of the SM-DP+ that the device should contact. Changing where your BSS sends new orders leaves those codes pointing to the original address. For outstanding orders, keep the original download path available or arrange replacement codes for subscribers who still need to activate.
That depends on the subscriber provisioning interface your HSS exposes. In OVOO’s integration, creating the HSS subscriber record triggers profile creation. The management backend places and confirms the order separately over ES2+. We would validate that sequence with your HSS before proposing changes to it.
Keep the profile’s ICCID with the commercial order so support can identify the exact profile involved in a failed download. If the target eUICC is known, its EID identifies the chip. That distinction matters when a subscriber has several profiles or has just replaced a handset.
Match the cancellation request to the profile’s ICCID and check the order state. For a pending download order, request cancellation over ES2+ and use the response to update the BSS. If the profile is already installed, follow your process for ending service on that subscription.
A Bound Profile Package is encrypted for one eUICC. A replacement handset with a different eUICC cannot install that package. The replacement process needs to authorise a new download for the new chip.
Test the handset firmware, LPA and eUICC combination you plan to support. Run a successful installation with the intended certificate chain, then test a certificate rejection. This gives support a way to recognise a trust failure before investigating the profile download itself.
The eSIM supplies the credentials for Wi-Fi sign-in. The handset also needs a Passpoint profile, and the access points must advertise the operator’s PLMN. In OVOO’s integration, a RADIUS proxy connects the access points to AAA, which authenticates subscribers using EAP-AKA and HSS data. For acceptance, trace one session from automatic sign-in through to the usage record in your charging system.
Tell us how you provision subscribers today and where eSIM fits into your offer. We can work through the BSS and HSS integration, agree the target devices and follow one subscription from order to installation.
