Basic meaning of roaming
Roaming refers to when a terminal leaves the coverage area of its home operator network and accesses services through the visited network. The visited network and the home core network work together through roaming protocols and settlement mechanisms to perform authentication, billing, and routing. For consumer mobile phones, roaming is highly transparent; for IoT, roaming is still often constrained by SIM card policies, APN, SMS gateways, and data plans. If a device is in border highways, ports, or cross-border logistics and its roaming capability has not been verified in advance, it may encounter situations like "can register but cannot transmit data" or "traffic taking a long detour causing latency spikes."
Architecture and data paths
In traditional roaming, the user plane might go through the home network gateway (Home Routed), causing access to local servers to take a longer route; local breakout can reduce latency but depends on operator policies and DNN configuration. IoT SIM cards bound to a fixed private address range need to confirm whether the address is still reachable and whether NAT sessions are re-established during roaming. Some M2M cards have international roaming disabled by default or allow only data without SMS, which needs to be individually confirmed in the project contract.
Module and SIM-side verification
Before mass production, road testing should be conducted on the target visited network: record registered PLMN, TAC/LAC, APN activation results, and round-trip delay. If using multiple IMSI switching or eUICC, it is necessary to verify the profile switching trigger conditions and failure fallback. For scenarios where only specific visited operators are allowed, this can be achieved through EF_PLMNwAcT or module network lock functions, but remote operation and maintenance methods should be retained in case of changes in operator cooperation.
Compliance and business risks
Cross-border data transmission may involve data localization regulations, and changes in roaming paths can affect compliance boundaries. High-cost roaming traffic may lead to uncontrolled OPEX, so usage thresholds and alarms should be set on the platform side. If the business relies on SMS configuration delivery, it is necessary to confirm roaming SMS routing and delay to avoid edge cases where "the device has arrived in another country, but the configuration is still queued at the home SMS center."
Engineering Practice Supplement
Cross-team collaboration for "IoT roaming": hardware provides impedance and power budget, RF provides spurious and sensitivity margins, embedded systems clarify thread models and storage lifespan, cloud clarifies SLA and rate limiting. For NB-IoT and similar scenarios, the business model must match wake-up cycles, packet length, and downlink capacity; for vehicular and mobile scenarios, session continuity during switching and roaming should be considered. At project completion, conduct a "red team" type retrospective: check whether defined behaviors exist for weak networks, power loss, certificate expiration, clock jumps, and full storage.
Home-Routed User Plane and Local Breakout
While roaming, the radio network is the visited one. Identity and charging still belong to the home operator. The authentication request goes back to the home network, and only after it passes is the terminal registered on the visited network. Data has two typical paths. The user plane can hairpin back to the home gateway and only then go out, which is home routing: a server near the visited place still takes the long way around. Local breakout hands the traffic off in the visited place. Delay is shorter, but the address, the firewall, and private-network routes all have to be redone for the breakout exit. IoT SIMs often have international roaming off by default, data on and SMS off, or an allow-list of visited networks. Those limits are written in the SIM and the subscription. Finding a signal does not let the module break them.
Before use, drive-test on the real visited network. Do not only flip a roaming switch on the home network and look once. Record the network that registered, the location area, whether the access point activated, the address obtained, and the delay to the service server. A fixed private address may be unreachable after roaming, and a network-address-translation mapping is rebuilt. When switching among several identities, or remotely replacing the SIM profile, define which identity to fall back to on failure, so the device does not stop in a state neither side accepts.
Attached, Then Refused by Policy
The most common picture is a terminal that shows registered, then a refused access-point activation, because the visited network has no interworking for that access point, or the home side has not enabled data roaming. The second is a service that works but with delay high enough to time the session out, because the user plane hairpins home and the application still retransmits as if delay were a few tens of milliseconds locally. The third is configuration that depends on SMS. The device is already abroad, the SMS is still queued at the home SMS center, and parameters stay behind the location. If the device is locked to one visited network and there is no remote way to unlock it, the whole lot goes offline when that partner stops the agreement.
Set a usage threshold on the platform. Otherwise the charge for hairpinned traffic is noticed only at the end of the month. Whether data still has to leave the country depends on which side the breakout sits. The device's geographic position is not enough. Which activation produced the address is in PDP context. Whether the radio returns to idle immediately after registration, so the first packet has to set up again, is in RRC states. Both are misreported as roaming failure.
The drive-test record should separate registration, activation, and service. Registration success only means the visited network accepted the identity. Activation failure is usually the access point or the data-roaming policy. Activation success with very high delay means looking at whether the user plane hairpins home or already exits locally. Writing the three as one "roaming failure" sends people to change the antenna, the SIM, and the server timeout at the same time. SMS configuration has to be checked for delivery time on its own. Data connectivity does not stand in for SMS reachability. A lock to a visited network must keep a remote way to remove the lock. Otherwise the device cannot change network after the partner stops cooperating. Usage alarms should be estimated from visited-place rates, not from the home plan's unit price. Hairpinned traffic can cost a great deal while the volume is still small. Which country's exit the data leaves from has to be read together with data-residency requirements. A device standing at a border does not mean the message did not return to the home country.