Description
The FRMCS Functional Identity is a key identifier concept in the Future Railway Mobile Communication System, defined in 3GPP specifications 22.889 and 22.989. It represents an identity related to a user or related to the equipment that indicates a special role, as specified in section 9.3 'Role management and presence'. This identity allows the entity to be addressed based on its role rather than just its individual user or device identity. For example, a functional identity might represent the 'Driver of train number 1234', enabling other parties to contact the driver of that specific train without knowing the driver's personal identity. The functional identity is central to role-based communication, which is a fundamental requirement in railway operations where roles are more important than individuals.
In the FRMCS architecture, functional identities are managed by the role management and presence service. When a user logs in or a device registers, it can assume a role, and the system associates a functional identity with that role. This identity is then used for addressing and presence. For instance, the control centre can call the functional identity of the driver of a particular train, and the call will be routed to the device currently associated with that role. The functional identity can be related to a user (e.g., a specific driver) or to equipment (e.g., a cab radio assigned to a train). This flexibility ensures that communication can be established based on operational needs rather than personal contact details.
The functional identity is distinct from other identifiers such as the user's subscription identity (e.g., IMPI) or the equipment's identity (e.g., IMEI). It is a logical identity that can be dynamically assigned and reassigned as roles change. For example, when a driver takes over a train, their user identity is linked to the functional identity of that train's driver. The system maintains a mapping between functional identities and the current users or equipment, enabling presence and reachability. This mapping is crucial for mission-critical communications, where knowing who is performing which role is essential for coordination and safety.
The concept of functional identity is closely tied to the role management and presence enablers defined in 3GPP mission-critical services (MCX). FRMCS builds on these enablers and adds railway-specific requirements. The functional identity is used in various FRMCS services, including voice, video, and data. It also supports group communications, where groups can be defined based on functional identities (e.g., all drivers of a certain train type). The identity can be used in addressing schemes, such as URIs or numbers, and is resolved by the network to the current endpoint.
In summary, the FRMCS Functional Identity is a role-based identifier that enables flexible, operational communication in railway environments. It allows parties to address roles rather than individuals, ensuring that critical communications reach the right person or device at the right time. Its definition has remained stable across releases, reflecting its fundamental importance to the FRMCS system.
Purpose & Motivation
The FRMCS Functional Identity exists to support role-based communication, which is essential in railway operations. In a railway environment, communication often needs to be directed to a role rather than a specific person. For example, a signaller needs to contact the driver of a particular train, but may not know who that driver is or their personal contact details. The functional identity provides a stable address for the role, allowing communication to be established regardless of which individual is currently performing the role. This is particularly important for safety-critical communications, where delays in reaching the right person can have serious consequences.
Historically, railway communications systems like GSM-R used functional numbers (e.g., train numbers) to address roles. However, these systems had limited flexibility and were not integrated with modern IP-based services. The FRMCS Functional Identity builds on this concept but integrates it with 3GPP mission-critical services, providing a standardized, flexible, and secure way to manage roles and presence. It solves the problem of dynamic role assignment: as staff change shifts or move between trains, the functional identity remains constant, and the system updates the mapping to the current user or device. This ensures that communication is always directed to the correct role holder.
Furthermore, the functional identity enables advanced features such as presence (knowing whether a role is currently staffed) and group communication (addressing multiple roles simultaneously). It also supports integration with railway back-office systems, allowing roles to be managed centrally. The functional identity is a cornerstone of the FRMCS system's ability to meet the operational communication needs of railways, ensuring that the right information reaches the right role at the right time.
What changed in its specifications
The latest release-to-release comparison of specifications that define FRMCS Functional 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 Functional 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 |