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

Understand · 1.6

Voice and operational reachability

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

Guiding question: Which functions help reach the correct participants in the appropriate form and with the appropriate urgency?

Learning objective: You explain role-based addressing, group communication and priority.

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

Different questions about the same exchange

A communication service from 1.5 must do more than transmit speech. It must include the intended participants and regulate their participation. For this introduction, we organise these needs into five groups of functions. This is a teaching structure, not a complete or mutually exclusive classification in a standard.

1. Group calls and broadcasts. A group call enables communication with a defined group. Participants can contribute to the shared conversation within the intended rules. The right to speak, or floor permission, is permission to inject speech at that moment. It determines whose speech contribution may currently be transmitted. In the GSM-R group call considered here, mobile participants speak in turn. A broadcast call, by contrast, sends the initiating participant's speech to the others, who listen within that call. Feedback therefore needs another means. [S01]

2. Priority and pre-emption. Priority means intended precedence. Pre-emption is the possible displacement of lower-priority communication in favour of higher-priority communication. It describes an intervention, not just a ranking. Applicable rules and configuration determine whether and how pre-emption occurs. [S01]

3. Railway emergency call. This is a special urgent communication for the operational participants defined for it. Recipients, area and precedence are part of its definition. It is neither merely a louder call nor automatically a call to every train in a country. [S01]

4. Functional addressing. This selects a destination through an operational function. Niko calls the current driver role of train 1234, rather than always calling Lea regardless of duty. The assignment to the currently responsible person must therefore be correct. [S02]

5. Location-dependent addressing. This takes the relevant location or area of responsibility into account when selecting a destination. Lea needs the signaller responsible for her section. In the original case, that is Niko. A different area may require a different assignment. [S02]

Combining functions

These five groups are not five mutually exclusive buttons. An urgent group exchange needs both a set of recipients and rules for speaking and precedence. Conversely, a correct recipient group does not mean everyone may speak simultaneously.

FRMCS retains corresponding operational needs, while technical procedures and their mapping may differ. FRMCS requirements address functional identities and hazard communication, among other things. We follow implementation further in 2.7 and 2.8. [S05]

Check your understanding

Match and justify: A A team needs two-way feedback. B One person speaks while everyone else only listens within that call. C An existing connection is ended in favour of a more urgent one. D Niko seeks the current driver. E Lea seeks the office responsible for her section. What additional definition does hazard communication need?

Model answer

A fits a group call, B a broadcast, C pre-emption, D functional addressing and E location-dependent addressing. Hazard communication additionally requires, in particular, defined recipients, the relevant area and priority behaviour. Several of these properties may be needed in the same exchange.

What to remember

  • Recipients, floor permission and priority are separate properties.
  • Role and location answer different destination questions.
  • The same operational purpose does not prove an identical technical procedure.

Your Talbahn case file

Add the Lea–Amir role change and Niko's area of responsibility. Describe an announcement and an exchange with feedback.

Sources

  • S01 · UIC EIRENE FRS

    UIC EIRENE FRS

    Version: 8.1.0 · Checked: 2026-10-11

    Scope: Functional requirements: voice functions, groups, priority and functional addressing.

    Limitations: Teaching reference; determine applicable requirements and MI markings for the project.

    Used in: 1.1, 1.2, 1.3, 1.6

  • S02 · UIC EIRENE SRS

    UIC EIRENE SRS

    Version: 16.1.0 · Checked: 2026-10-11

    Scope: Section 1.4 architecture; requirements for GSM-R system functions and addressing.

    Limitations: No blanket statement about every installed GSM-R implementation.

    Used in: 1.3, 1.5, 1.6, 1.8

  • S05 · UIC FRMCS FRS FU-7120

    UIC FRMCS FRS FU-7120

    Version: 2.1.0, 29 April 2025 · Checked: 2026-10-11

    Scope: Functional requirements, identities, Functional Alias, voice and hazard communication.

    Limitations: Teaching foundation, not evidence of complete product support.

    Used in: 1.2, 1.3, 1.6, 2.7, 2.8, 2.15, 2.20, 3.2

Shared source register

Your progress is stored in this browser on this device.