Description
Railway Emergency Communication (REC) is a standardized service within 3GPP that leverages cellular networks, primarily 5G, to provide mission-critical communication for railway systems. It is designed to meet the stringent reliability, availability, and latency requirements of railway operations, particularly during emergencies. The architecture integrates with existing railway communication systems and the 3GPP core network, utilizing network slicing and priority mechanisms to guarantee service quality. Key components include the User Equipment (UE) on trains, the Radio Access Network (RAN), and the 5G Core Network (5GC), which together facilitate secure and immediate communication channels.
REC operates by establishing dedicated communication sessions with high priority and pre-emption capabilities over public or private 5G networks. It employs Quality of Service (QoS) mechanisms to ensure low latency and high reliability for emergency calls and data transmissions. The service supports group communication, enabling coordinated responses among multiple parties such as train drivers, control center operators, and emergency services. It also incorporates location-based services to provide accurate positioning of trains, which is crucial during incident management.
The role of REC in the network is to provide a standardized, interoperable solution for railway emergency communications, replacing or augmenting legacy systems like GSM-R. It ensures that critical information can be exchanged swiftly and reliably, supporting functions such as emergency braking notifications, incident reporting, and evacuation coordination. By leveraging 5G advancements, REC enhances situational awareness and response times, contributing to overall railway safety and operational resilience.
Purpose & Motivation
REC was created to address the limitations of existing railway communication systems, such as GSM-R, which lack the bandwidth, low latency, and advanced features required for modern railway operations. The increasing complexity of railway networks, including high-speed trains and automated systems, necessitated a more robust and future-proof emergency communication solution. 3GPP introduced REC to leverage the capabilities of 5G technology, providing enhanced reliability, capacity, and service integration for critical railway communications.
The primary problem REC solves is ensuring uninterrupted and high-priority communication during emergencies, where delays or failures could lead to severe safety incidents. It provides a standardized framework that ensures interoperability across different railway operators and regions, facilitating seamless communication in cross-border scenarios. Historical context includes the evolution from analog systems to digital GSM-R, and now to IP-based 5G systems, driven by the need for higher data rates, lower latency, and support for new applications like video surveillance and real-time data analytics.
REC also addresses the growing demand for integrating railway communications with public safety networks, enabling coordinated responses with external emergency services. By utilizing network slicing, REC can create virtual dedicated networks for railway operations, ensuring resource isolation and guaranteed performance even during network congestion. This approach future-proofs railway communications, supporting emerging technologies such as autonomous trains and predictive maintenance.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (20 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-16, normative work from Rel-18.
In Release 18, the REC function was enhanced to introduce MCX Service Ad hoc Group Communication as an alternative capability for supporting Railway Emergency Communication. The release also specified procedures for interworking with GSM-R, such as inviting an FRMCS user to a voice communication, and introduced mechanisms for triggering a change of communication privileges for a user based on identities or talker status. Furthermore, alignment was made between the procedures for changing conditions and merging of Railway Emergency Alerts.
- Adding MCX Service Ad hoc Group Communication as alternative capability to support Railway Emergency Communication TS 22.989CR0012
- Changes to Critical Support Applications “Inviting-a-FRMCS User to a voice communication” use case TS 22.989CR0002
- Merging of Railway Emergency Communications TS 22.989CR0003
- 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
- Alignment between Changing conditions of Railway Emergency Alert and Merging Railway Emergency Alert TS 22.989CR0010
+ 1 more changes
In Release 19, the Railway Emergency Communication (REC) function was enhanced with new and clarified use cases, including specific procedures for **Public Train Emergency Communication** and **Railway Staff Emergency Communication**. The release also introduced updates for **Multi-train voice communication for Drivers and Ground FRMCS User(s)**, refining the related initiation and termination procedures. Furthermore, the scope was expanded through a comprehensive clean-up and gap analysis of existing REC use cases, alongside an update to quality of service (QoS) considerations tailored for the railway operational environment.
- Virtual Coupling data communication use case TS 22.989CR13
- Public Train Emergency Communication related use cases TS 22.989CR17
- Railway staff Emergency Communication related use cases TS 22.989CR18
- Enhancement and clean-up of Railway Emergency Communication related use cases TS 22.989CR16
- Enhancement of Multi-train voice communication for Drivers and Ground FRMCS User(s) related use cases TS 22.989CR0019
- Update of QoS in a railway environment Use Case TS 22.989CR0021
+ 4 more changes
In Release 20, the REC function was enhanced with new use cases and updated requirements for multi-train voice communication. Specifically, the release introduced the capability for both a Train Controller (a Ground FRMCS User) and a train driver to initiate the merging of two multi-train voice communications. Furthermore, the requirements and gap analysis for this ad hoc group communication function for Drivers and Ground FRMCS Users were updated.
- New use cases: Merging of two multi-train voice communications by Train Controller (Ground FRMCS user) TS 22.989CR0033
- New use cases: Merging of two multi-train voice communications by the train driver TS 22.989CR0037
- 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
Explore further
Broader topics and technologies where REC plays a role.
Defining Specifications
3GPP specifications that define or reference REC, 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 |
| TR 22.989 vk30 | FRMCS Analysis and Requirements | Rel-20 |