Description
The Train Driver is a specific user role defined within the Future Railway Mobile Communication System (FRMCS) framework, which is being standardised by 3GPP in close cooperation with the railway sector (notably UIC and ETSI). FRMCS is the successor to GSM-R, the current railway communications standard, and is designed to run over 3GPP LTE and 5G networks. Within this framework, the term "Driver" refers to a Mobile FRMCS User who has been provisioned with special capabilities by the FRMCS System. These capabilities go beyond those of ordinary railway users and are tied to the safety-critical nature of train driving.
Architecturally, the Driver is a user role defined at the application layer of the FRMCS system, which sits on top of the 3GPP network. The FRMCS System includes a set of application functions such as the FRMCS Application Server, the FRMCS User Management function, and the FRMCS Security functions. When a driver logs in (typically via a FRMCS cab radio or a handheld terminal), the system authenticates the user and retrieves the associated profile. The profile determines which services the driver can invoke, such as railway emergency calls, direct mode communication, functional addressing, and location-dependent addressing. The special capabilities may include priority handling, access to train control data, and the ability to initiate railway emergency calls that pre-empt other traffic.
The Driver role is closely linked to the concept of the FRMCS User Identity (FRMCS ID) and the FRMCS Service Profile. The FRMCS System manages these profiles and can update them dynamically. For example, when a driver takes over a train, the system may associate the driver's identity with the train's identity, enabling functional addressing such as "call the driver of train 1234". This is a key feature of FRMCS, as it decouples communication from specific terminal equipment and allows calls to reach the driver regardless of which terminal they are using.
From a 3GPP perspective, the Driver role is defined in technical specifications 22.889 (Study on Future Railway Mobile Communication System) and 22.989 (Future Railway Mobile Communication System). These specifications describe the service requirements and the user roles. The Driver is one of several roles, alongside other roles such as Signaller, Shunter, and Trackside Worker. Each role has different capabilities and priorities. The Driver role is particularly important because the driver is responsible for the safe movement of the train and must be able to communicate with the signaller and other railway staff in normal and emergency situations.
The special capabilities granted to the Driver are enforced by the FRMCS System through a combination of application-level authorisation and network-level QoS and priority mechanisms. For instance, the 3GPP network can provide priority treatment to the driver's traffic using mechanisms such as Access Class Barring, QoS Class Identifiers (QCIs), and the 5G QoS Indicator (5QI). The FRMCS System may also use the 3GPP Public Warning System (PWS) or Mission Critical Push-to-Talk (MCPTT) capabilities to deliver railway emergency calls. The Driver role therefore exemplifies how 3GPP networks can support vertical industries by providing tailored user roles and service capabilities.
Purpose & Motivation
The Driver role exists to ensure that train drivers have reliable, prioritised access to the communication services they need for safe and efficient train operation. In the legacy GSM-R system, the driver's communication needs were met through dedicated cab radios with limited functionality. As railways move to FRMCS over 3GPP networks, there is a need to define user roles explicitly so that the system can grant appropriate privileges and ensure that safety-critical communications are not degraded by other traffic.
The special capabilities granted to the Driver address several problems. First, they ensure that the driver can always reach the signaller, even during network congestion, by using priority and pre-emption mechanisms. Second, they enable the driver to initiate railway emergency calls that override other communications. Third, they allow the driver to be reached via functional addressing, which is essential when the driver is not in their usual cab or when multiple drivers are operating in the same area. Finally, the Driver role supports the integration of train control data and voice services, which is a key requirement for future autonomous train operation.
The definition of the Driver role in 3GPP specifications provides a standardised basis for interoperability across different railway operators and equipment vendors. Without such a definition, each vendor might implement its own proprietary role model, leading to fragmentation and increased costs. By defining the Driver as a Mobile FRMCS User with special capabilities, 3GPP enables a consistent approach to authorisation, priority, and service invocation across the entire railway ecosystem.
What changed in its specifications
The latest release-to-release comparison of specifications that define Driver (Train Driver). 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.
Initial definition introduced in 3GPP specifications 22.889 and 22.989: "A Mobile FRMCS User provided with special capabilities by the FRMCS System." This established the Driver as a distinct user role within the emerging FRMCS framework, which was being studied as the successor to GSM-R.
Defining Specifications
3GPP specifications that define or reference Driver (Train Driver), 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 |