Description
FRMCS Roaming is the capability defined in 3GPP TS 22.889 and TS 22.989 that allows a FRMCS User to make use of FRMCS Applications in a Visited (FRMCS) Network. In the railway context, a train equipped with FRMCS Equipment crosses national borders and administrative domains frequently, and the on-board users and applications must retain access to railway-specific services regardless of which network currently provides radio coverage. Roaming therefore is not a convenience feature but a core operational requirement for international rail corridors.
Architecturally, FRMCS Roaming builds on the 3GPP roaming framework but extends it with railway-specific considerations. The Home FRMCS Network holds the subscription, credentials and service profile of the FRMCS User, while the Visited FRMCS Network provides the 3GPP transport (radio access and core connectivity) and may host or provide access to application servers. Authentication and authorization are anchored in the home network, while the visited network enforces local policy and provides the bearer for the FRMCS Applications. The FRMCS System definition explicitly includes the FRMCS Equipment, the 3GPP transport and the application servers, and roaming must preserve the end-to-end service across these components even when they are split between home and visited domains.
Operationally, FRMCS Roaming must support both human users (drivers, dispatchers, on-board staff) and machine users (train control, telemetry, sensor systems). Because FRMCS Users can be connected via 3GPP RAT, wired connectivity or other radio technology, the roaming solution must be agnostic to the access technology and focus on service continuity at the application layer. This is particularly relevant for mission-critical railway applications such as train-to-ground communication, where interruption during a border crossing could affect safety and punctuality.
The roaming relationship also interacts with network slicing and QoS. A visited network must be able to honor the slice and QoS profile associated with the FRMCS subscription so that critical applications receive the same treatment as in the home network. This requires exchange of slice and QoS information between home and visited networks, and mechanisms to ensure that the visited network can admit the FRMCS User with the required guarantees.
Finally, FRMCS Roaming has implications for security and management. Cross-domain trust must be established between operators, credentials must be protected, and charging and settlement must account for usage in the visited network. The term has remained stable across Releases 16 through 20, indicating that the high-level definition of roaming has been settled while detailed normative work on slices, QoS and security continues in the underlying specifications.
Purpose & Motivation
FRMCS Roaming exists because railway operations are inherently cross-border and multi-operator. A train travelling along an international corridor will pass through coverage provided by different network operators and different countries, yet the on-board FRMCS Users and applications must continue to operate without interruption. Without roaming, each operator would need to provision and manage separate subscriptions for every network along the route, which is operationally and commercially impractical.
The concept addresses the limitations of legacy railway communication systems, which were largely national and based on dedicated technologies such as GSM-R. Those systems did not provide a general framework for a user to access railway applications in a visited network using commercial 3GPP transport. FRMCS, built on 3GPP technology, inherits the mature roaming machinery of cellular networks but must adapt it to railway-specific requirements such as mission-critical QoS, network slicing and the mix of human and machine users.
By defining roaming at the service level, 3GPP enables a FRMCS User to be authenticated by their home network while consuming applications and connectivity in a visited network. This supports competition among operators, simplifies cross-border operations, and allows railway undertakings to contract with a home operator while relying on visited networks for coverage. The stable definition from Rel-16 onward reflects that the fundamental requirement has been understood early, with subsequent releases focusing on the detailed mechanisms needed to realize it.
What changed in its specifications
The latest release-to-release comparison of specifications that define FRMCS Roaming. Each summary describes the whole specification, not only this term.
Rel-16 added FRMCS use cases and requirements for rail communication, covering safety, train control, interworking, and network management.
Full comparison in TR 22.889 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference FRMCS Roaming, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 22.889 vh40 | FRMCS Study; Stage 1 | Rel-17 read |
| TR 22.989 vk30 | FRMCS Analysis and Requirements | Rel-20 read |