Skip to content
Independent reference on the Future Railway Mobile Communication System

Understand · 1.7

ETCS, ATO and other railway applications

Time: about 8–11 minutes including the task; estimate

Guiding question: Why does an application's task determine the communication it needs?

Learning objective: You separate ETCS and ATO responsibilities from their communication provision.

Prerequisites: Previous lessons through 1.6, particularly the case file developed there.

From data volume to meaning

The workshop analyses temperature files. Niko needs an operational report. Both exchanges carry data, but their purposes differ. File size alone therefore says nothing about how quickly or reliably the information is needed.

Here, criticality describes the significance of a failure for the use case under consideration. What matters is the consequence of missing, incorrect or late information. The term does not replace a formal safety assessment; initially it helps ask the right questions.

A temperature file for analysis tomorrow can wait under the assumed conditions. If the same measurement is used for an imminent protective decision, the requirements change. “Measurement data are non-critical” would therefore be as wrong as “voice is always most important”.

Train protection and automated driving

ETCS stands for European Train Control System. It performs train-control and protection tasks: it supervises permitted running conditions and can intervene when necessary, for example in an overspeed situation. In radio-based applications, on-board and trackside systems exchange information for this purpose. [S03, S18]

ATO stands for Automatic Train Operation. It automates specified driving tasks, such as acceleration and braking. Which tasks the system performs and which remain with staff depend on the implementation and grade of automation. ATO does not automatically mean driverless operation. [S32]

Communication enables information exchange between the applications involved. It does not itself issue a movement authority, independently supervise permitted speed or independently perform the driving task. In ATO over ETCS, automated driving tasks and ETCS supervision therefore remain distinct.

What FRMCS changes

FRMCS is intended to provide communication capabilities for such applications. Changing the radio network does not automatically replace ETCS equipment or introduce ATO. In our case file, ETCS and ATO are therefore additional planning cases, not already confirmed equipment on train 1234.

For each planning case, Talbahn asks: which parties exchange which information? By when must it be available? What are the consequences of its absence? What response does the application provide? Only then are appropriate transport and service requirements formulated.

GSM-R is already used for voice and ETCS data communication. The difference from FRMCS is therefore not “conversations instead of train data”, but a development of the underlying communication system. [S03, S04]

Check your understanding

One system supervises permitted running conditions; another automates driving tasks; a third transmits information. Which tasks belong to ETCS, ATO and communication? Then explain why a small message can be more urgent than a large file.

Model answer

ETCS performs supervision, ATO the specified automated driving tasks, and communication the exchange of information. The small message may be needed for an immediate decision while the file is analysed tomorrow. Purpose and consequences matter, not data volume. This example does not establish a universal priority order for all files and messages.

What to remember

  • Communication and the application's operational function are different.
  • Criticality follows from the use case and possible consequences.
  • Performance requirements are justified from application needs.

Your Talbahn case file

Add consequences and required timeliness for both familiar pairs of communication partners. Record ETCS and ATO as additional planning cases.

Sources

  • S03 · ERA: European Rail Traffic Management System

    ERA: European Rail Traffic Management System

    Version: Web overview · Checked: 2026-10-11

    Scope: Relationship between ETCS and railway communication.

    Limitations: Orientation; use S18/S30 additionally for specific ETCS statements.

    Used in: 1.1, 1.2, 1.3, 1.7

  • S04 · UIC: FRMCS

    UIC: FRMCS

    Version: Web overview, checked 11 October 2026 · Checked: 2026-10-11

    Scope: General context; FRMCS introduction situation; specifications.

    Limitations: Support around 2035 is an expectation; TSI 2027 is a planning reference. Cross-check procurement claims against S16/S37.

    Used in: 1.1, 1.4, 1.7, 1.9

  • S18 · UNISIG SUBSET-023: ERTMS/ETCS Glossary

    UNISIG SUBSET-023: ERTMS/ETCS Glossary

    Version: 4.0.0 · Checked: 2026-10-11

    Scope: ETCS, RBC and associated terminology.

    Limitations: Terminology reference, not complete ETCS system training.

    Used in: 1.7, 2.16

  • S32 · ERTMS/ATO Glossary

    ERTMS/ATO Glossary

    Version: Version 2, 5 July 2023 · Checked: 2026-10-11

    Scope: ATO and separation of tasks in the ETCS context.

    Limitations: No claim that FRMCS alone introduces ATO.

    Used in: 1.7

Shared source register

Your progress is stored in this browser on this device.