{"id":35679,"date":"2021-07-06T15:14:11","date_gmt":"2021-07-06T14:14:11","guid":{"rendered":"https:\/\/www.gsma.com\/solutions-and-impact\/technologies\/internet-of-things\/?page_id=35679"},"modified":"2025-12-04T11:59:40","modified_gmt":"2025-12-04T11:59:40","slug":"roaming","status":"publish","type":"page","link":"https:\/\/www.gsma.com\/solutions-and-impact\/technologies\/internet-of-things\/mobile-iot\/roaming\/","title":{"rendered":"Mobile IoT (LPWA) roaming"},"content":{"rendered":"\n
\n
\"A<\/span>
\n

Mobile IoT (LPWA) roaming<\/h1>\n\n\n\n

Mobile IoT (LPWA) roaming enables a mobile subscriber to LTE-M or NB-IoT networks to seamlessly connect their IoT devices, and access associated IoT services across countries and networks.<\/p>\n\n\n\n\n\n

<\/div><\/div>\n<\/div><\/div>\n<\/div>\n\n\n\n
<\/div>\n\n\n\n

Mobile IoT roaming enables this freedom while maintaining use of a SIM from the same service provider – even when IoT devices move outside the geographical coverage area of their home network. Mobile IoT (LPWA) roaming is technically enabled by inter-operator mobility management, authentication and billing procedures. Establishing roaming between network operators is based on the commercial terms contained in dedicated roaming agreements.<\/p>\n\n\n\n

Benefits of Mobile IoT (LPWA) roaming<\/h3>\n\n\n\n

Mobile IoT (LTE-M and NB-IoT) are the only true LPWA roaming networks. As part of the global cellular network family its offers the same benefits of security, billing and control through a SIM that you get with 2G\/3G\/4G\/5G. Mobile IoT is the only standard for LPWAN defined in 3GPP. It is not proprietary and only operates in licenced spectrum – something to be aware of when roaming because unlicensed spectrum can be used in other countries for other purposes without notice.<\/p>\n\n\n\n

Backed by the worlds leading mobile networks with over 40 years operational experience managing 10 billion connections, you can be sure you have the best quality and service that you need for your roaming IoT solution.<\/p>\n\n\n\n

Mobile IoT (LPWA) roaming features<\/h3>\n\n\n\n
<\/i><\/div>
NB-IoT Features in Roaming<\/div><\/div>
<\/p>\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Deployment band(s)<\/strong><\/td>\nFrequency bands of LPWA technology and associated deployment method. (These are InBand, GuardBand or StandAlone). <\/strong><\/td>\n<\/tr>\n
IP Roaming<\/td>\nIP version support for inbound roamers (IPv4, IPv6 and\/or dual-stack)<\/td>\n<\/tr>\n
RRC Activity Timer<\/td>\nTimer controlling how long a Mobile IoT device is held in connected mode. Important from a battery consumption perspective as most of power consumption occurs during connected mode<\/td>\n<\/tr>\n
Non-IP roaming<\/td>\nSupport of non-IP data delivery (NIDD) for inbound roamers. Non-IP data can be transferred back to your home network via the service capability exposure function (SCEF). The delivery of this data to the customer\u2019s application server can be via a REST API or a message protocol such as MQTT. Alternatively, non-IP data is transferred back to the customer\u2019s application server via the packet gateway. Delivery of this data to the customer\u2019s application server is then via UDP encapsulation and may also use dedicated backhaul (e.g. IPSec).<\/td>\n<\/tr>\n
Data transport via control plane<\/td>\nSupport of IP data delivery for inbound roamers over the control plane<\/td>\n<\/tr>\n
Data transport via user plane<\/td>\nSupport of IP data delivery for inbound roamers using the user plane and IP.<\/td>\n<\/tr>\n
Release assistance indication<\/td>\nRelease assistance indication enables IoT applications to reduce device power consumption. It allows a Mobile IoT device to drop to idle mode as soon as it has finished sending data rather than remaining in connected mode until the expiration of the base station\u2019s RRC activity timer.<\/td>\n<\/tr>\n
Power saving mode<\/td>\nPower saving mode helps devices save battery power and achieve longer battery lives by allowing a device to enter a \u201cdeep-sleep.\u201d Whilst in \u201cdeep sleep\u201d, the Mobile IoT device is unreachable.<\/td>\n<\/tr>\n
Data packet buffering for PSM<\/td>\nA mobile IoT device is unreachable when it is in \u201cdeep sleep\u201d. When the Mobile IoT device awakens, a mobile IoT network supporting data packet buffering will forward data packets it had temporarily held for that Mobile IoT device whilst it was unreachable. If data packet buffering is enabled in a Mobile IoT network, the maximum number and size of the buffered packets is determined by each mobile network operator.<\/td>\n<\/tr>\n
Long periodic tracking area update<\/td>\nLong periodic tracking area update is used in conjunction with PSM. The periodic tracking area update timer (T3412) determines how long a Mobile IoT device can remain in idle or deep sleep mode before it must reconnect and send a tracking area update message to the base station.<\/td>\n<\/tr>\n
Extended discontinuous reception (eDRX)<\/td>\nExtended discontinuous reception can be used by IoT devices to reduce power consumption. eDRX can be used without PSM or in conjunction with PSM to obtain additional power saving. By momentarily switching off the receive section of the radio chipset for a brief period, Mobile IoT devices are able to save power.<\/td>\n<\/tr>\n
Data packet Buffering for eDRX<\/td>\nSimilar to data packet buffering for PSM, a Mobile IoT network supporting data packet packet buffering for eDRX will temporarily hold data packets for the brief period the Mobile IoT device has switched it\u2019s receiver off to reduce energy consumption. If data packet buffering is enabled in a Mobile IoT network, the maximum number and size of the buffered packets is determined by each mobile network operator.<\/td>\n<\/tr>\n
SMS support<\/td>\nNative support for mobile terminating and Mobile originating SMS services on NB-IoT.<\/td>\n<\/tr>\n
UE power classes<\/td>\nThe 3GPP Mobile IoT standards define several transmit power classes. Power classes with lower output power may allow a Mobile IoT device to reduce battery energy consumption although the lower power output may impact the distance the device may be located from a base station.<\/td>\n<\/tr>\n
CE levels \/ coverage enhancement<\/td>\nMobile IoT devices are able to operate using different coverage enhancement levels which provide the ability for a Mobile IoT device to work in locations where regular mobile devices may not have coverage.<\/td>\n<\/tr>\n
GTP-IDLE timer on IPX firewall<\/td>\nWhen a Mobile IoT device roams onto another network, a GTP tunnel is established between the home and visited networks to carry data between the Mobile IoT device in the visited network and it\u2019s home network. It is common for timers to be used in IPX firewalls between mobile operators to determine how long the GTP tunnel remains open and how long the device may remain inactive without losing this connection. For example, the value of this timer is critical for the efficient use of the PSM feature when roaming otherwise the Mobile IoT device may awaken from it\u2019s deep sleep to find the GTP tunnel has been disconnected.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

\n<\/div><\/div>\n\n\n\n

<\/i><\/div>
LTE-M Features in Roaming<\/div><\/div>
<\/p>\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Deployment band(s)<\/strong><\/td>\nFrequency bands of LPWA technology<\/strong><\/td>\n<\/tr>\n
IP roaming<\/td>\nIP version support for inbound roamers (IPv4, IPv6 and\/or Dual-stack)<\/td>\n<\/tr>\n
RRC activity timer<\/td>\nTimer controlling how long a Mobile IoT device is held in connected mode. Important from a battery consumption perspective as most of power consumption occurs during connected mode.<\/td>\n<\/tr>\n
Data transport via control plane<\/td>\nSupport of IP data delivery for inbound roamers over the Control Plane<\/td>\n<\/tr>\n
Data transport via user plane<\/td>\nSupport of IP data delivery for inbound roamers using the user plane and IP.<\/td>\n<\/tr>\n
Release assistance indication<\/td>\nRelease assistance indication enables IoT applications to reduce device power consumption. It allows a Mobile IoT device to drop to idle mode as soon as it has finished sending data rather than remaining in connected mode until the expiration of the base station\u2019s RRC activity timer.<\/td>\n<\/tr>\n
Power saving mode<\/td>\nPower saving mode helps devices save battery power and achieve longer battery lives by allowing a device to enter a \u201cdeep-sleep \u201d. Whilst in \u201cdeep sleep\u201d, the Mobile IoT device is unreachable.<\/td>\n<\/tr>\n
Data packet buffering for PSM<\/td>\nA mobile IoT device is unreachable when it is in \u201cdeep sleep\u201d. When the Mobile IoT device awakens, a mobile IoT network supporting data packet buffering will forward data packets it had temporarily held for that Mobile IoT device whilst it was unreachable. If data packet buffering is enabled in a Mobile IoT network, the maximum number and size of the buffered packets is determined by each mobile network operator.<\/td>\n<\/tr>\n
Long periodic tracking area update<\/td>\nLong periodic tracking area update is used in conjunction with PSM. The periodic tracking area update timer (T3412) determines how long a Mobile IoT device can remain in idle or deep sleep mode before it must reconnect and send a tracking area update message to the base station.<\/td>\n<\/tr>\n
Extended discontinuous reception (eDRX)<\/td>\nExtended discontinuous reception can be used by IoT devices to reduce power consumption. eDRX can be used without PSM or in conjunction with PSM to obtain additional power saving. By momentarily switching off the receive section of the radio chipset for a brief period, Mobile IoT devices are able to save power.<\/td>\n<\/tr>\n
Data packet buffering for eDRX<\/td>\nSimilar to data packet buffering for PSM, a Mobile IoT network supporting data packet packet buffering for eDRX will temporarily hold data packets for the brief period the Mobile IoT device has switched it\u2019s receiver off to reduce energy consumption. If data packet buffering is enabled in a Mobile IoT network, the maximum number and size of the buffered packets is determined by each mobile network operator.<\/td>\n<\/tr>\n
SMS support<\/td>\nNative support for mobile terminating and mobile originating SMS services on LTE-M.<\/td>\n<\/tr>\n
UE power classes<\/td>\nThe 3GPP Mobile IoT standards define several transmit power classes. Power classes with lower output power may allow a Mobile IoT device to reduce battery energy consumption although the lower power output may impact the distance the device may be located from a base station.<\/td>\n<\/tr>\n
Voice support (VoLTE)<\/td>\nSupport of VoLTE service over LTE-M for inbound roamers with an IMS subscription<\/td>\n<\/tr>\n
CE Levels \/ coverage enhancement<\/td>\nMobile IoT devices are able to operate using different coverage enhancement levels which provide the ability for a Mobile IoT device to work in locations where regular mobile devices may not have coverage.<\/td>\n<\/tr>\n
GTP-IDLE timer on IPX firewall<\/td>\nWhen a Mobile IoT device roams onto another network, a GTP tunnel is established between the home and visited networks to carry data between the Mobile IoT device in the visited network and it\u2019s home network. It is common for timers to be used in IPX firewalls between mobile operators to determine how long the GTP tunnel remains open and how long the device may remain inactive without losing this connection. For example, the value of this timer is critical for the efficient use of the PSM feature when roaming otherwise the Mobile IoT device may awaken from it\u2019s deep sleep to find the GTP tunnel has been disconnected.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

\n<\/div><\/div>\n\n\n\n

Additional coverage information<\/h3>\n\n\n\n
\n
Mobile IoT deployment map<\/a><\/div>\n\n\n\n
Mobile IoT commercial launches<\/a><\/div>\n\n\n<\/div>\n\n\n\n

Mobile IoT roaming – operator settings (version October 2025)<\/h3>\n\n\n\n
\n
Operator LTE-M settings<\/a><\/div>\n\n\n\n
Operator NB-IoT settings<\/a><\/div>\n<\/div>\n\n\n\n

<\/p>\n\n\n\n

Please submit your roaming features to IoTMarketing@gsma.com<\/strong>.<\/p>\n\n\n\n

Wholesales Agreements and Solutions (WAS) Group<\/h3>\n\n\n\n

The Wholesale Agreements and Solutions Group (WAS) is responsible for operator-to-operator and operator-to-hub interoperability (including interworking and roaming) providing GSMA Members with a consistent, reliable service for members to offer their customers.<\/p>\n\n\n\n

The Wholesale Agreements and Solutions Group (WAS) develops roaming and interconnect agreement templates and wholesale charging principles. Additionally, WAS supports GSMA programs and projects with the development of roaming and interconnect agreement templates and wholesale charging principles that are unique to the needs of these efforts, as appropriate.<\/p>\n\n\n\n

For more information, please visit: https:\/\/www.gsma.com\/get-involved\/working-groups\/wholesale-agreements-and-solutions-group\/<\/a> or InfoCentre2<\/sup> membership\/member-gateway\/<\/p>\n\n\n\n

Mobile IoT (LPWA) roaming announcements<\/h3>\n\n\n\n