Description
A FRMCS User, as defined in 3GPP TS 22.889 and TS 22.989, is a human user or a machine making use of the railway-specific communication. This broad definition is deliberate: FRMCS must serve not only people such as train drivers, dispatchers and on-board staff, but also automated systems including train control, telemetry, sensors and other machine-type applications. By covering both human and machine users in a single term, 3GPP ensures that requirements address the full range of railway communication needs.
The definition also specifies that FRMCS Users can be connected via 3GPP RAT, wired connectivity or other radio technology. This access-agnostic stance is important because railway environments include trains, trackside infrastructure and control centres with diverse connectivity options. A driver's handheld device may use a 3GPP radio access technology, while trackside sensors may be connected by wire, and other systems may use alternative radio technologies. The FRMCS User concept focuses on the user and the service consumed rather than on the underlying access, allowing 3GPP to specify requirements that apply consistently across access types.
In the architecture of the FRMCS System, FRMCS Users interact with FRMCS applications hosted on application servers, using the 3GPP transport for connectivity. The user's identity, subscription and service profile determine which applications they can access, what QoS they receive, and whether they can roam into visited networks. For human users, this may involve authentication and authorization through credentials; for machine users, it may involve device identities and automated authentication mechanisms.
The FRMCS User term is foundational for other requirements. FRMCS Roaming is defined in terms of a FRMCS User making use of applications in a visited network. QoS and priority requirements are expressed in terms of the needs of different FRMCS Users, with mission-critical users such as train control receiving preferential treatment. Security requirements address the protection of FRMCS Users' communications and identities. Management requirements cover the provisioning and monitoring of FRMCS Users across the system.
The definition has remained unchanged from Rel-15 through Rel-20, reflecting a stable understanding of who the users of FRMCS are. This stability allows subsequent releases to focus on detailed normative work on services, QoS, security and roaming without revisiting the fundamental scope of the user population.
Purpose & Motivation
The FRMCS User concept exists to define the scope of railway communication from the user perspective. Railway communication involves a wide range of participants, from drivers and dispatchers to automated train control systems and trackside sensors. Without a clear definition of who the users are, requirements could become fragmented or fail to address important use cases. By defining FRMCS User to include both human users and machines, 3GPP ensures that the specifications cover the full spectrum of railway needs.
The access-agnostic aspect of the definition addresses the reality that railway communication is not limited to a single access technology. Legacy systems were tied to specific technologies, but FRMCS is designed to work across 3GPP radio, wired connections and other radio technologies. This flexibility allows railway operators to use the most appropriate connectivity for each situation, whether it is a handheld device on a train, a wired sensor in a tunnel, or a specialized radio system for a particular application.
The term also provides a basis for differentiating service levels. Not all FRMCS Users have the same requirements: a train control system may need ultra-reliable low-latency communication, while a passenger information system may tolerate higher latency. By defining the user as the entity that consumes railway communication, 3GPP can specify QoS, priority and security requirements that are tied to the user and the application, rather than to the access technology. This supports the development of network slicing and mission-critical services that are essential for the future of railway operations.
What changed in its specifications
The latest release-to-release comparison of specifications that define FRMCS User. 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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (7 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- Changes to Critical Support Applications “Inviting-a-FRMCS User to a voice communication” use case TS 22.989CR0002
- Changes to Critical Support Applications Inviting-a-FRMCS User to a voice communication use case to support Interworking with GSM-R TS 22.989CR0004
- Triggering a change of communication privileges for a particular FRMCS User based on identities and/or talker status TS 22.989CR0008
- New use cases: Merging of two multi-train voice communications by Train Controller (Ground FRMCS user) TS 22.989CR0033
- New use case: Availability status of a MC User (Presence of a FRMCS User) TS 22.989CR0038
- Update of requirements and gap analysis for multi-train voice communication for Drivers and Ground FRMCS User(s) using Ad hoc Group Communications TS 22.989CR0032
Defining Specifications
3GPP specifications that define or reference FRMCS User, 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 |