Definition
PLMN (Public Land Mobile Network) consists of the MCC (Mobile Country Code) and MNC (Mobile Network Code), used to uniquely identify an operator's network. When IoT SIM cards roam to a visited network, the terminal decides the order and target of registration based on the PLMN-related lists stored in the SIM/USIM files (such as User Controlled PLMN Selector, Operator Controlled PLMN Selector, Forbidden PLMN, etc.), the broadcast PLMNs available in the radio environment, the device's manual or automatic mode, and OTA updates sent by the network. The preferred selection strategy determines how to prioritize certain operators or frequency bands under multiple available network conditions to balance communication quality, cost, latency, compliance, and operational accessibility.
Consumer mobile phone users can manually select networks, while IoT batch devices usually run fully automatically. Card providers and project teams must write the PLMN list and roaming policies correctly before issuing cards; otherwise, devices may stay long-term on expensive or poor-quality networks or repeatedly search for networks, consuming extra power. In some countries, multiple operators may share the RAN but have different core networks, so PLMN display and billing attribution need to be specially verified.
Preferred selection does not mean "always lock to the strongest signal"; it also needs to consider roaming partner settlement, whether the IoT SIM card's data plan covers the visited PLMN, and whether special provisions like allowing NB-IoT roaming are permitted.
Technical key points
After the terminal powers on, it first attempts to attach to the home PLMN (HPLMN). If that fails, it scans according to the order in the OPLMN/UPLMN list and then selects based on signal quality. The network can send updates related to the RPLMN (Registered PLMN) or influence subsequent selection through ANDSF or URSP (5G) policies. When the eUICC downloads a new profile, the PLMN list is replaced entirely along with the profile; this mechanism is commonly used in cross-border deployments to implement "local preference."
Locking to a network (IMSI lock, band lock, manually specifying a PLMN) can improve behavior predictability but reduces resilience: there is no automatic fallback if the primary operator fails. Some IoT modules support configuring preferred PLMN through AT commands, which should align with SIM file strategies to avoid conflicts between commands and EF files that could cause abnormal reselection.
When multimode terminals switch between 2G/4G/5G, the set of available PLMNs may differ. Historical legacy paths, such as "falling back to 2G due to the lack of a 4G roaming agreement," may occur; it is necessary to confirm the local 2G network shutdown schedule.
IoT SIM cards and platform configuration
Confirm the roaming partner list with the SIM provider, whether automatic network selection optimization is enabled, and whether high-risk PLMNs are prohibited. The connection management platform can statistically track the current RPLMN distribution by visited country and issue alerts if abnormal clustering is found. For customers sensitive to charges, the contract can stipulate "prohibit access to specified high-rate MNCs," and FPLMN updates or module policy instructions can be delivered via OTA to enforce this.
When using VPDN for backhauling to the enterprise side, the entry DNS and routing for different visited PLMNs may be different. It's necessary to verify tunnel stability in the lab across major partner networks. The eUICC project should prepare tested Profile templates for each target country to avoid discovering that some PLMNs do not have an IoT APN after deployment.
The platform application layer should tolerate changes in roaming IP segments to avoid misjudging the roaming exit as an attack source; at the same time, update geofencing rules to prevent risk control triggers based on incorrect country codes.
Operation and Troubleshooting
The phenomenon "no service for a long time after going abroad" may be due to the SIM not being enabled for roaming in that country, the terminal not supporting the local band, or being incorrectly barred by the FPLMN. The phenomenon "can register but no data" is often due to the visited site not having an IoT APN enabled or a DNS failure. By comparing the RPLMN logs of devices from the same batch in different countries, it is possible to quickly identify whether the issue is a policy problem or a single point hardware failure.
Roaming tariff disputes often originate from the terminal residing in a high-rate network unexpectedly. It is necessary to retrieve the PLMN registration records for the time period and verify them against the carrier's billing statements. If network searching consumes excessive power, check if the list is too long or if signal edge reselection occurs repeatedly; if necessary, tighten the band or increase reselection hysteresis.
During major international exhibitions or sporting events, local carrier congestion may make the preferred network unavailable. Backup roaming partners and manual remote Profile switching plans should be prepared.
Compliance and Security
Data cross-border transmission is affected by the roaming path. Some visited locations have legal requirements for local offloading or prohibit backhaul to third countries. PLMN selection directly affects compliance risk. When sanction countries and entity lists are updated, the list of PLMNs prohibited for access should be immediately revised and delivered via OTA. Audits should retain registration history for regulatory inquiries.
High-security scenarios should monitor abnormal PLMN residency (which may indicate a SIM card being stolen for remote access) and coordinate with TAC change detection.
Use Cases
Scenarios that rely on global roaming of IoT SIM cards, such as cross-border logistics, international fleet management, deep-sea container tracking, and overseas construction machinery leasing, are particularly sensitive to PLMN selection. Consumer electronics going overseas, overseas charging stations, and multinational retail POS also need to solidify roaming strategies before mass production. Devices with fixed national borders must prevent mistakenly registering on neighboring high-cost networks, usually assisted by geofencing and power control.
SimtoLink provides multi-country roaming IoT SIM cards, profile planning, and connectivity data analysis, helping customers implement executable PLMN strategies balancing cost, experience, and compliance.