Description
The FRMCS User Identity is a fundamental identifier defined within the 3GPP framework for the Future Railway Mobile Communication System (FRMCS), which is the successor to GSM-R for railway communications. It represents the identity by which a FRMCS User can be addressed, meaning it serves as the addressing handle that allows the network and other users to reach a specific railway communication user. This identity is specified in 3GPP TS 22.889 (Study on Future Railway Mobile Communication System) and TS 22.989 (Future Railway Mobile Communication System requirements), which together define the service requirements for FRMCS.
In the FRMCS architecture, users are not limited to human operators but can include functional identities associated with train drivers, dispatchers, shunting personnel, trackside workers, and automated railway functions. The FRMCS User Identity provides a stable, network-independent reference that can be used for call setup, functional addressing, and service authorization. Unlike a simple subscriber identity such as an IMSI, the FRMCS User Identity is designed to support railway-specific operational models where roles and functions matter more than individual device subscriptions.
The identity plays a central role in functional addressing, a key FRMCS requirement inherited from GSM-R. Functional addressing allows a caller to reach a user based on their current role or function (for example, the driver of a particular train) rather than a fixed directory number. The FRMCS User Identity underpins this capability by providing the persistent reference against which functional numbers and location-dependent addressing can be resolved.
From a security and management perspective, the FRMCS User Identity is used for authorization and access control. The network can verify that a given user identity is entitled to specific services, such as mission-critical push-to-talk, railway emergency calls, or priority handling during congestion. This ties the identity to the broader 3GPP mission-critical services framework, including MCX (MCPTT, MCVideo, MCData) enablers.
The identity also supports mobility and roaming scenarios. As trains move across administrative boundaries and network domains, the FRMCS User Identity remains constant, allowing consistent service delivery and seamless handover between networks. This is essential for cross-border railway operations where a train may traverse multiple countries and network operators.
In terms of standardization evolution, the definition of FRMCS User Identity has remained stable from Release 15 through Release 20. The wording "The identity by which a FRMCS User can be addressed" has been carried over unchanged across all these releases, indicating that the fundamental concept was well-established at introduction and did not require revision as the FRMCS specifications matured. This stability is notable given that FRMCS as a whole evolved significantly over the same period, with new service requirements and architectural refinements being added.
Purpose & Motivation
The FRMCS User Identity exists to provide a stable, standardized way to address and identify users within the Future Railway Mobile Communication System. Railway communications have unique requirements that differ from public mobile networks: users are often associated with functions or roles rather than individual devices, and addressing must work reliably across organizational and national boundaries. The identity solves the problem of how to consistently reach a train driver, dispatcher, or trackside worker regardless of which device or network they are currently using.
Historically, GSM-R provided railway-specific identities and functional numbering, but these were tightly coupled to GSM technology and lacked the flexibility needed for modern broadband services. As railways migrate toward 5G-based FRMCS, there was a need to redefine user identities in a way that aligns with 3GPP mission-critical service frameworks while preserving railway operational concepts such as functional addressing and priority communications.
The FRMCS User Identity addresses the limitations of device-centric identities by decoupling the user from the underlying subscription. This enables role-based communication, supports seamless mobility across network boundaries, and provides a foundation for authorization and service entitlement in a multi-vendor, multi-operator environment.
What changed in its specifications
The latest release-to-release comparison of specifications that define FRMCS User Identity. 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 User Identity, 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 |