---
title: "Jietion (@globaliotsim) | Hashnode"
description: "Business Development at Quanqiu IoT. Read the latest articles by Jietion on Hashnode."
url: "https://hashnode.com/@globaliotsim"
---

@globaliotsim

# Jietion

@globaliotsim · Guangzhou, China · Joined October 2026

Business Development at Quanqiu IoT

[Website](https://www.globallotsim.com/)

## Comments

[Good question. It depends on where the check sits and how the roaming traffic is routed. Most roaming IoT SIMs use home routing: the data session goes back to the issuer's packet gateway (PGW or GGSN). The device's IMEISV is normally carried in the session setup (the MEI field of the GTP Create Session Request), so a lock enforced at that gateway behaves the same at home and abroad. The visited network only passes the request through. It changes in two cases: Local breakout. The session ends on a gateway in the visited network, so the home check never sees the data session. The lock may then only apply at registration, if at all. Missing IMEI. The MEI field is conditional, so a visited core can omit it. A lock that blocks when the IMEI is absent will cut off good devices in that country. One that allows it will not catch a swap there. What we would do in practice is test it rather than treat roaming as a general exception. In each target country, put a bound SIM into a different device and confirm the session is refused, then check that the platform logs the IMEI it saw. Where the IMEI comes through, keep the lock. Where it does not, turn the missing IMEI into an alert rather than a block, and rely on usage and location monitoring there. One unrelated thing that looks the same in the field: national IMEI registries (Turkey, Indonesia) can block an unregistered device with no SIM lock involved.](https://hashnode.com/posts/imei-lock-for-iot-sims-device-binding-misuse-detection-and-device-swap-policies/6af31a45a607a9c1e147bc52/comment/6af334e13b8023106a82aecf#reply-6afa9cd67ffdb7288ca8836d)

Reply · Article · 3d ago · [IMEI Lock for IoT SIMs: Device Binding, Misuse Detection and Device-Swap Policies](https://hashnode.com/posts/imei-lock-for-iot-sims-device-binding-misuse-detection-and-device-swap-policies/6af31a45a607a9c1e147bc52)

[Thanks, and good tip on logging charge per report cycle. It is the quickest way to separate retry spikes from the baseline. On your question: in weak-signal sites the retries usually dominate. Each failed attach or resend keeps the radio at its highest current for seconds, while PSM/eDRX timers mostly set the floor between reports. The two interact, though: the network can grant shorter PSM or eDRX timers than the device requested, so the unit wakes more often, and in poor coverage every extra wake brings its own retry series. So we would first check the timers the network actually granted (AT+CEREG=4 shows the granted T3412/T3324), then count retries per cycle. Randomised back-off after failures, as GSMA TS.34 recommends, also stops a whole site from retrying at the same moment.](https://hashnode.com/posts/battery-powered-iot-sensors-power-budgets-lpwan-choice-and-sim-settings-for-underground-and-remote-sites/6ac98d1a25f15888a5677cec/comment/6ad208a8da8aaf54c3145f83#reply-6adb89d5c414037f9634908c)

Reply · Article · Oct 23 · [Battery-Powered IoT Sensors: Power Budgets, LPWAN Choice and SIM Settings for Underground and Remote Sites](https://hashnode.com/posts/battery-powered-iot-sensors-power-budgets-lpwan-choice-and-sim-settings-for-underground-and-remote-sites/6ac98d1a25f15888a5677cec)
