Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Controller (Train Controller)

Train Controller (FRMCS Ground User)

Services →

Controller (Train Controller) Controller (Train Controller) controller (Train Controller) is a Ground FRMCS User granted special capabilities by the FRMCS System, enabling railway operational control functions over the Future Railway Mobile Communication System.

Introduced
Rel-15
Where
Services
Specifications
2 specs
Controller (Train Controller) Description Purpose What changed Neighbours Specifications

Description

The Train Controller is a role defined within the Future Railway Mobile Communication System (FRMCS) user model, specified in 3GPP TS 22.889 (Study on Future Railway Mobile Communication System) and TS 22.989 (FRMCS User Requirements). FRMCS is the successor to GSM-R, the railway communications standard that has served European and other railways for decades but is approaching end of life. 3GPP developed FRMCS requirements to define how 5G and its successors can carry railway mission-critical voice and data services, including train control, shunting, and operational communications.

In the FRMCS user model, users are categorised by their functional role and by whether they are ground-based or on-board. The Train Controller is a Ground FRMCS User—meaning the person operates from a fixed or ground-based environment rather than aboard a train—who is provided with special capabilities by the FRMCS System. These special capabilities distinguish the Train Controller from ordinary railway users such as drivers or trackside workers. They typically include the ability to initiate and manage group calls to trains and trackside staff, to monitor train positions and status, to issue operational instructions with high priority, and to invoke functional identities and roles that carry elevated privileges within the railway communication system.

The FRMCS architecture separates the communication service layer from the underlying 3GPP network. The FRMCS System comprises application functions, the FRMCS Application Server, and interfaces to the 3GPP core network (typically 5G System with mission-critical services such as MCX—Mission Critical Push To Talk, MCData and MCVideo). The Train Controller interacts with the system through a FRMCS application on a fixed control desk or mobile device. The 'special capabilities' granted to this role are enforced by the FRMCS System through authorisation, priority handling, and functional alias management, ensuring that only authorised controllers can exercise control functions.

Because railway operations demand extremely high reliability and availability, the Train Controller role is tied to mission-critical service requirements: priority and pre-emption, group communication with short setup times, and resilience against network degradation. The FRMCS System must ensure that a Train Controller can always reach the trains under their control, even during congestion or partial network failure. This is why the role is explicitly modelled in the requirements specifications rather than left to application-level implementation.

The definition has remained unchanged from Rel-15 through Rel-20, indicating a stable role model established early in the FRMCS requirements work. As FRMCS moves from study to normative specification and deployment, the Train Controller remains a central persona around which mission-critical railway communication services are designed.

Purpose & Motivation

The Train Controller role exists because railway operations require a clearly identified, privileged human actor who can direct train movements and coordinate responses to incidents over the radio system. In legacy GSM-R, train controllers used dedicated voice dispatch functions with priority access. As railways migrate to FRMCS over 5G, 3GPP needed to formalise the roles and capabilities that the new system must support, so that vendors and operators build interoperable mission-critical services.

Defining the Train Controller as a Ground FRMCS User with special capabilities allows the FRMCS System to apply differentiated treatment: authorisation checks, priority and pre-emption, functional aliases, and group communication management. Without such a definition, each railway administration might implement controller functions differently, undermining interoperability across borders and between suppliers—a critical concern in rail, where trains cross national boundaries.

The definition also supports security and safety analysis: knowing which users hold elevated capabilities allows the system to protect those capabilities against misuse. Its stability from Rel-15 onward reflects that the role model was well understood from the outset, drawing on decades of GSM-R operational experience.

What changed in its specifications

The latest release-to-release comparison of specifications that define Controller (Train Controller). Each summary describes the whole specification, not only this term.

TR 22.889Rel-15 → Rel-16

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.

Rel-15 Initial

Initial definition introduced in the FRMCS study and requirements work: a Ground FRMCS User provided with special capabilities by the FRMCS System. This established the privileged controller role within the emerging 5G-based railway communication model.

Definition text carried over unchanged from Rel-15.

Definition text carried over unchanged from Rel-15.

Definition text carried over unchanged from Rel-15.

Definition text carried over unchanged from Rel-15.

Definition text carried over unchanged from Rel-15.

Defining Specifications

3GPP specifications that define or reference Controller (Train Controller), with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 22.889 vh40 FRMCS Study; Stage 1 Rel-17 read
TR 22.989 vk30 FRMCS Analysis and Requirements Rel-20 read