WATP

Wayside Automatic Train Protection

IoT →
Introduced in Rel-16

WATP is a 3GPP railway system feature that uses wayside equipment and mobile network connectivity to transmit vital safety commands from a central control to trains for automatic train protection.

Category
IoT
Introduced
Rel-16
Where
Services
Specifications
2 specs
WATP Description Purpose Related Classification Detected Changes Specifications

Description

Wayside Automatic Train Protection (WATP) is a standardized architecture within 3GPP that supports railway safety-critical control systems by utilizing 3GPP mobile network technology for communications between trains and wayside infrastructure. Automatic Train Protection is a fundamental safety system that continuously monitors train speed and position, enforcing safe movement authorities (MAs) to prevent collisions, derailments from excessive speed, and incursions into occupied track sections. Traditional ATP relies on balises (beacons) on the track or continuous track circuits, which are expensive to install and maintain.

The WATP architecture introduces a wireless, network-based approach. Key components include the On-Board Unit (OBU) on the train, which contains the vital ATP logic; the Wayside ATP Unit (WAU), which is the trackside equipment that determines movement authorities based on track occupancy and interlocking status; and the 3GPP network (4G LTE or 5G NR), which provides the communication bearer between them. The WAU connects to the mobile network as a User Equipment (UE) or via a fixed network connection to a dedicated server. It uses 3GPP-defined services, potentially enhanced for ultra-reliable low-latency communication (URLLC), to transmit Movement Authority (MA) messages to the target train's OBU.

How it works involves a continuous cycle of determination and transmission. The Wayside ATP Unit calculates a safe movement profile (including target speed and braking curve) for a train based on the train's reported position (via GNSS or other sensors), the status of signals and switches from the interlocking, and the known positions of other trains. This vital MA message is then packetized and sent over the 3GPP network to the specific train, addressed using its network identity (e.g., IP address). The train's OBU receives this message, validates its integrity and authenticity using security mechanisms, and then compares the authorized MA against the train's actual speed and position. If a violation is detected (e.g., speeding), the OBU automatically initiates braking to bring the train to a safe state. The system requires extremely high levels of reliability, availability, and low latency, which are addressed by 5G NR features like URLLC, network slicing, and device-to-device communications for direct train-to-train alerts.

Purpose & Motivation

WATP was created to modernize and reduce the cost of railway signaling and safety systems by leveraging commercial off-the-shelf mobile network technology. Traditional train protection systems, such as track circuits, axle counters, and lineside balises, require extensive physical infrastructure installed along the entire railway corridor. This results in very high capital expenditure (CAPEX) for new lines and significant operational expenditure (OPEX) for maintenance, especially in harsh environments or over long, remote distances.

The primary problem WATP solves is providing a flexible, scalable, and cost-effective alternative for ATP, particularly for regional or low-density lines where installing traditional systems is economically prohibitive. It also addresses the need for continuous, high-capacity data exchange for future railway operations, such as real-time video for obstacle detection or condition-based monitoring, which legacy systems cannot support. The motivation for its standardization in 3GPP Rel-16 was the recognition of railways as a key vertical industry for 5G, with specific requirements for mission-critical communication that could be met by enhancing existing 3GPP standards rather than developing completely separate, proprietary wireless solutions.

It addresses the limitations of previous wireless solutions for railways, which were often isolated, proprietary networks (like GSM-R), offering limited bandwidth and an aging technology base. WATP, built on 4G/5G, provides a migration path to a future-proof, IP-based platform that can support both safety-critical ATP and other operational/ passenger services on a shared infrastructure, enabled by network slicing to ensure isolation and performance guarantees for the safety slice.

Classification

Part ofURLLC
Related approachesFRMCSV2X

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (15 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-16, normative work from Rel-17.

Rel-17 1 change

In Release 17, the specification introduced new requirements for the On-Network communication mode of the Future Railway Mobile Communication System (FRMCS), which underpins the WATP function. This included a complete analysis to define the necessary capabilities for FRMCS Equipment, such as functional identities and roles, to operate reliably over the 3GPP network. These enhancements ensure the FRMCS System can support critical railway protection services like automatic train control within the new architecture.

  • Complete analysis for Rel-17 On-Network FRMCS requirements TS 22.889CRSP-200882
Rel-18 5 changes

In Release 18, the WATP function was enhanced through new capabilities for the FRMCS System to automatically trigger a change of communication privileges for a specific FRMCS User based on their identities or talker status. Furthermore, the release introduced arbitration procedures with an automatic answer feature and refined service interworking between FRMCS and GSM-R, specifically removing the requirement for presence service interworking. These updates provided more automated and privilege-aware control for critical railway communications.

  • 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
  • Arbitration: automatic answer TS 22.989CR0009
  • Service interworking between FRMCS and GSM-R of presence is no more required TS 22.989CR0011
Rel-19 4 changes

In Release 19, the WATP (Wayside Automatic Train Protection) function was enhanced through new use cases for Public Train Emergency Communication and for Multi-train voice communication for Drivers and Ground FRMCS Users. These additions specifically expanded the operational scenarios and communication capabilities for safety-critical interactions between trains, drivers, and ground-based systems like the Radio Block Centre (RBC). Furthermore, the release introduced enhancements to the FRMCS naming authority to improve identity management for functional roles and equipment within the FRMCS System.

  • Real-time automatic translation of languages related use cases TS 22.989CR14
  • Public Train Emergency Communication related use cases TS 22.989CR17
  • Enhancement of Multi-train voice communication for Drivers and Ground FRMCS User(s) related use cases TS 22.989CR0019
  • Enhancement of FRMCS naming authority use case TS 22.989CR0023
Rel-20 5 changes

In Release 20, the WATP function was enhanced with new use cases for multi-train voice communications, specifically enabling a Train Controller or a train driver to merge two such communications. Furthermore, new capabilities were introduced for monitoring the availability status of an FRMCS User and allowing a train driver to take over an Ad hoc Group Call from another FRMCS device. These updates were accompanied by a revised requirements and gap analysis for multi-train voice communication used by Drivers and Ground FRMCS Users.

  • 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
  • New use case: Availability status of a MC User (Presence of a FRMCS User) TS 22.989CR0038
  • New use case: Train driver takes-over an Ad hoc Group Call from another FRMCS device TS 22.989CR0036
  • 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 WATP plays a role.

Defining Specifications

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

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