# eSIM (eUICC) usage with RC7630

**URL:** <https://forum.sierrawireless.com/t/esim-euicc-usage-with-rc7630/35676>\
**Category:** IoT Modules\
**Created:** [December 17, 2025, 6:05am UTC](https://forum.sierrawireless.com/t/esim-euicc-usage-with-rc7630/35676 "2025-12-17T06:05:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![minhyuk.lee](https://avatars.discourse-cdn.com/v4/letter/m/8dc957/32.png) [@minhyuk.lee](https://forum.sierrawireless.com/u/minhyuk.lee)\
**Post date:** [December 17, 2025, 6:05am UTC](https://forum.sierrawireless.com/t/esim-euicc-usage-with-rc7630/35676/1 "2025-12-17T06:05:57Z")

</div>

We are currently evaluating the **RC7630** module for an IoT product and would like to clarify the supported options regarding **eSIM (eUICC) usage and profile provisioning**.

Specifically, we would like to understand the following points:

1. **eUICC Compatibility**

2. **Profile Provisioning Method**

3. **LPA Support**

4. **Download vs. Activation Control**

5. **Recommended Approach**

Our intent is to determine whether we can source eSIMs independently, or if we should rely on **vendor-supplied or vendor-approved eSIM solutions** to ensure full compatibility and GSMA compliance.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [December 17, 2025, 6:14am UTC](https://forum.sierrawireless.com/t/esim-euicc-usage-with-rc7630/35676/2 "2025-12-17T06:14:59Z")

</div>

Some discussion regarding internal esim of rc76

> [@eSIM in RC76xx](https://forum.sierrawireless.com/t/esim-in-rc76xx/25816/4):
>
> Hi saim, eSIM is designed for OTA and Connectivity Ready services on RC76XX.

If you use your own eSIM, you might need to get a tool from distributor to disable the internal LPA inside module stack so that you can run your own external LPA on host platform

---

<div class="post-metadata">

**Author:** ![minhyuk.lee](https://avatars.discourse-cdn.com/v4/letter/m/8dc957/32.png) [@minhyuk.lee](https://forum.sierrawireless.com/u/minhyuk.lee)\
**Post date:** [December 18, 2025, 11:30am UTC](https://forum.sierrawireless.com/t/esim-euicc-usage-with-rc7630/35676/3 "2025-12-18T11:30:37Z")

</div>

Based on your explanation, I would like to clarify the LPA architecture in more detail.

If the LPA is implemented externally (for example, on a Linux host OS or a PC application),  
is it technically supported to:

• Run the LPA logic (SM-DP+ communication, profile management) outside the modem  
• And then use AT commands or QMI only as a transport channel to send APDUs / profile data to the eUICC inside the RC7630?

In other words,  
can the modem act purely as an APDU tunnel to the eUICC,  
while the full LPA (per GSMA SGP.02 / SGP.32) runs on an external host?

Or is the LPA required to be integrated inside the modem firmware and tightly coupled with the eUICC interface, making an external LPA + AT/QMI approach unsupported?

Any clarification on the supported architecture would be appreciated.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [December 18, 2025, 1:00pm UTC](https://forum.sierrawireless.com/t/esim-euicc-usage-with-rc7630/35676/4 "2025-12-18T13:00:35Z")

</div>

I think the lpa can be run in external host platform and controlled by AT command