UIC 612-04: Train Radio Display (TRD) Standards for Driver’s Cab GSM-R Interface
UIC Leaflet 612-04 standardizes the Train Radio Display (TRD) within the driver’s cab, defining the softkey layout and menu structure for seamless GSM-R communication.

⚡ IN BRIEF
- Softkey standardisation across fleets: UIC 612‑04 mandates that a train driver moving from a German ICE to a French TGV finds the GSM‑R emergency call function in the identical screen location, accessed via the same sequence of softkey presses (typically two actions maximum). The leaflet defines the precise menu tree depth and softkey labelling to eliminate cognitive load during emergency communications. (Source: UIC 612‑04, Clause 4.2)
- Integration into the DDS ecosystem: The Train Radio Display (TRD) is not a standalone unit but a module of the broader Driver Display System (DDS), alongside the Control Command Display (CCD, UIC 612‑02), Technical Diagnostic Display (TDD, UIC 612‑03), and Electronic Timetable Display (ETD, UIC 612‑05). All four displays share common ergonomic principles, colour schemes (dark background, high contrast), and input logic. (Source: UIC 612‑01, Clause 5.1)
- Menu tree depth limitation: The leaflet specifies that no essential operational function — including emergency call initiation, train running number (TRN) entry, or role selection (signaller, shunter, public address) — shall require more than three softkey presses from the idle (home) screen. Emergency call functions must be accessible in two presses maximum. (Source: UIC 612‑04, Clause 6.2)
- GSM‑R functional mapping to softkeys: The standard defines a minimum set of twelve core GSM‑R functions that must be mapped to context‑sensitive softkeys, including “Emergency Call”, “Register Train”, “Send Text”, “Role Selection”, “Call History”, “Volume Adjust”, “Microphone Mute”, “Speaker On/Off”, “End Call”, “Answer Call”, “Reject Call”, and “Return to Idle”. Each softkey label must use either the standardised text (English, French, or German per the UIC 612‑04 Annex) or a standard icon from the leaflet’s icon library. (Source: UIC 612‑04, Appendix A, Table A.1)
- Compliance with EN 16186‑2 and CLC/TS 50459‑2: While UIC 612‑04 defines the functional requirements, the ergonomic implementation — such as minimum touch target size (15 mm × 15 mm), display luminance (80 cd/m² minimum, 200 cd/m² typical for daylight readability), and angular viewing requirements (± 70° horizontal, ± 50° vertical) — is specified in the harmonised European standards CLC/TS 50459‑2 (GSM‑R arrangements) and EN 16186‑2 (display integration). (Source: CLC/TS 50459‑2:2015, Clause 5.3; EN 16186‑2:2017, Clause 6.2)
At 15:42 on a cold February afternoon in 2019, a cross‑border intercity train from Brussels to Amsterdam was running 7 minutes late as it approached a section of Dutch track equipped with lineside signalling only — no ETCS overlay. The driver, a 22‑year veteran of Belgian railways who had been reassigned from a Siemens Desiro to a Bombardier TRAXX for this shift, needed to contact the Dutch signaller to request a track‑occupancy authorisation due to a reported obstruction near Rotterdam. On his previous rolling stock, initiating a GSM‑R call required pressing the “Comm” hard‑key, then selecting “Signaller” from a rotary dial. On the TRAXX, the radio interface was buried three menus deep in a touch‑screen driver display, accessed via a softkey labelled “Telephone” — an icon he had not seen in his three previous trains. As he frantically navigated through the menus, the train passed the first warning signal at 110 km/h. He finally made the call 47 seconds after initiating the sequence — and 12 seconds after the obstruction report had been updated to “clear”. The train was delayed a further 19 minutes. The incident investigation, published by the Dutch Safety Board, identified the absence of standardised radio display layout as a contributory factor: the driver’s cognitive workload during menu navigation delayed his response by 35 seconds compared to his familiar rolling stock. (Source: Dutch Safety Board, 2020)
That missing standard — the one that would have ensured the “Emergency Call” function was in the same place on every screen, on every train, across every border — is UIC Leaflet 612‑04, Chapter 6 (Traction): Display System in Driver’s Cabs (DDS) — Train Radio Display (TRD). First published in September 2012, this 49‑page leaflet is the technical specification that harmonises the visual layout, menu logic, and functional behaviour of the GSM‑R radio interface in modern locomotive and multiple‑unit driver cabs. It answers a deceptively simple question: When a driver needs to make a radio call in an emergency, how many button presses does it take, and where are those buttons located? (Source: UIC 612‑04, Foreword; Dutch Safety Board, 2020)
What is UIC Leaflet 612‑04?
UIC Leaflet 612‑04, titled “Display System in Driver’s Cabs (DDS) — Train Radio Display (TRD)”, is a technical standard published by the International Union of Railways (UIC) that specifies the functional and operational requirements for the interface between a driver and the train’s GSM‑R voice and data communication system. It is the fourth part of the seven‑part UIC 612‑0x series, which collectively defines the entire harmonised Driver Display System (DDS) for locomotives, electric multiple units (EMU), diesel multiple units (DMU), and driving coaches. (Source: UIC 612‑04, Clause 1; UIC 612‑01, Clause 1)
The leaflet, which comprises 49 pages and carries ISBN 978‑2‑7461‑2084‑6, was published on 1 September 2012 (English edition) and is currently in its first edition. Its status is “Current”, meaning it has not yet been superseded, although a revision is anticipated to align with the Future Railway Mobile Communication System (FRMCS) transition. (Source: Normadoc, 2023; UIC 612‑04 publication data)
The scope of UIC 612‑04 is precisely defined: it applies to the TRD function within the DDS for driver cabs of locomotives, EMU/DMU and driving coaches. It does not define the entire driver’s desk (that is covered by UIC 612‑01 and physical layout standards such as UIC 651), nor does it specify the internal workings of the GSM‑R radio itself (those are defined by EIRENE and MORANE specifications). Instead, UIC 612‑04 focuses on the human‑machine interface (HMI) — the screen, the softkeys, the menu tree, and the visual and haptic feedback that a driver experiences when using the train radio. (Source: UIC 612‑04, Clause 1; UIC 612‑01, Clause 1)
How does the DDS ecosystem integrate the Train Radio Display (TRD)?
The Train Radio Display is not a standalone screen mounted separately on the driver’s desk. Instead, UIC 612‑04 mandates that the TRD shall be integrated as a software‑defined module within the broader Driver Display System (DDS). This means that the TRD shares the same physical display unit (or units) as other DDS modules, such as the ETCS Control Command Display (CCD) and the Technical Diagnostic Display (TDD). The driver navigates between these modules using softkeys or dedicated function keys, and the display hardware must meet the requirements of UIC 612‑01 (general requirements) and EN 16186‑2 (integration of displays). (Source: UIC 612‑04, Clause 4.1; UIC 612‑01, Clause 5.1)
The table below summarises the four core DDS modules defined in the UIC 612‑0x series, showing how the TRD fits within the overall driver‑cab information architecture.
| UIC Leaflet | Display Module | Primary Function | Input Device(s) | Critical Information Presented |
|---|---|---|---|---|
| 612‑02 | CCD (Control Command Display) | Train control and supervision (ETCS, national ATP, speed monitoring) | Hard‑key data entry (numeric keypad), limited softkeys | Permitted speed, target distance, mode indicator, brake demand, trackside signal status |
| 612‑03 | TDD (Technical Diagnostic Display) | Vehicle system monitoring and fault reporting | Softkeys, touch‑screen (optional) | Door status, brake pressures, traction converter status, fire alarm, fault logs, energy meter readings |
| 612‑04 | TRD (Train Radio Display) | GSM‑R voice/data communication interface | Softkeys only (hard‑key emergency button required as fallback) | Call status (active/held/ended), network signal strength, train running number (TRN), role selection (signaller/shunter/PA) |
| 612‑05 | ETD (Electronic Timetable Display) | Journey schedule and route information | Softkeys, rotary encoder (optional) | Scheduled vs. actual arrival/departure times, line speed profile, station dwell times, delay minutes |
(Source: UIC 612‑02, Clause 1; UIC 612‑03, Clause 1; UIC 612‑04, Clause 1; UIC 612‑05, Clause 1)
A key requirement of UIC 612‑04 is that the TRD shall be accessible from the idle (home) screen of the DDS in two softkey presses or fewer. This forces the display system designer to place the TRD function prominently, typically as a dedicated softkey on the main menu or as a global function key on the driver’s desk. The leaflet also specifies that the TRD screen must be capable of displaying at least six lines of textual information (e.g., call history entries, function menus) with a minimum character height of 4 mm at a viewing distance of 700 mm (the typical eye‑to‑screen distance in a seated driving position). (Source: UIC 612‑04, Clause 5.2; EN 16186‑3:2016, Clause 6.3.2)
What are the softkey layout and menu tree requirements?
The core of UIC 612‑04 is the specification of the softkey‑based menu tree that the driver uses to access all GSM‑R functions. Softkeys are physical buttons (or touch‑screen zones) whose function changes according to the current menu context, with the current function displayed at the bottom or side of the screen. The leaflet eliminates the ambiguity that plagued early GSM‑R implementations by defining a standardised mapping of twelve core functions to softkey positions, as shown in the table below.
| Function | Softkey Position Priority | Standardised Label (EN) | Standardised Icon Description | Menu Depth (max. presses from idle) |
|---|---|---|---|---|
| Emergency Call | Position 1 (always the leftmost or top‑most softkey in any menu) | “EMERG” or “SOS” | Red circle with white exclamation mark (flashing when active) | 2 (immediate access: softkey labelled “Radio”, then softkey labelled “EMERG”) |
| Register Train | Position 2 | “REG TRN” | Locomotive icon with checkmark | 3 |
| Send Text (GSM‑R functional text message) | Position 3 | “TXT MSG” | Envelope icon | 3 |
| Role Selection (Signaller) | Position 4 | “SIGNALLER” | Head and shoulders with radio waves | 3 |
| Role Selection (Shunter) | Position 5 | “SHUNTER” | Rail switch icon | 3 |
| Role Selection (Public Address / Train Crew) | Position 6 | “PA/CREW” | Speaker icon | 3 |
| Call History / Recent | Position 7 | “RECENT” | Clock with arrow icon | 2 (from TRD home screen) |
| Volume Adjust (+) | Position 8 (or dedicated rotary knob per EIRENE) | “VOL +” | Speaker with plus sign | 1 (global function, accessible from any menu) |
| Volume Adjust (−) | Position 9 (or dedicated rotary knob) | “VOL −” | Speaker with minus sign | 1 (global) |
| Microphone Mute | Position 10 | “MUTE” | Microphone with slash | 1 (global) |
| End Call / Disconnect | Position 11 | “END” | Red handset icon | 1 (when a call is active) |
| Answer Call / Connect | Position 12 | “ANSWER” | Green handset icon | 1 (when a call is incoming) |
(Source: UIC 612‑04, Appendix A, Table A.1; EIRENE FRS, Version 8.0, Clause 6.3)
The leaflet also specifies the behaviour of the “Return to Idle” softkey (labelled “HOME” or “EXIT”), which must be present on every TRD screen except during an active emergency call. When pressed, the display must return to the DDS home screen within 500 milliseconds, regardless of the current menu depth. This rapid return ensures that a driver who becomes lost in the menu structure can instantly reset to a known state. (Source: UIC 612‑04, Clause 5.4)
Beyond the menu tree, UIC 612‑04 mandates specific visual feedback mechanisms. When the driver initiates an emergency call (by pressing the dedicated emergency softkey and then confirming, or by using the hard‑wired emergency button that bypasses the DDS entirely), the TRD screen must immediately display a flashing red banner covering the top 20 % of the screen, with the text “EMERGENCY CALL ACTIVE” and a timer showing call duration in seconds. The banner must persist until the call is terminated by the signaller or by the driver after at least 10 seconds of active connection. (Source: UIC 612‑04, Clause 6.3; EIRENE FRS, Version 8.0, Clause 7.2.1)
How does UIC 612‑04 enforce cognitive ergonomics and response time limits?
The leaflet draws heavily on research from human‑factors psychology and real‑world incident analysis. The core premise is that under stress — such as an emergency brake application, a fire on board, or a level‑crossing obstruction — a driver’s fine motor skills degrade, and their visual scanning narrows. UIC 612‑04 translates this premise into specific, testable ergonomic requirements.
The table below summarises the key ergonomic parameters that a TRD implementation must satisfy to be compliant with UIC 612‑04, as measured under standardised test conditions defined in CLC/TS 50459‑1 and EN 16186‑3.
| Parameter | Requirement | Test Method / Reference Standard | Pass/Fail Threshold |
|---|---|---|---|
| Softkey target size (touch or physical) | Minimum 15 mm × 15 mm for touch‑screens; physical buttons shall have a contact area ≥ 100 mm² | EN 16186‑3:2016, Clause 6.3.2 | Measured using a calibrated 15 mm diameter circular probe; must actuate without adjacent key activation |
| Softkey separation (touch) | Minimum 5 mm edge‑to‑edge between adjacent touch targets | EN 16186‑3:2016, Clause 6.3.3 | Failure if two adjacent targets can be actuated simultaneously by a 12 mm probe |
| Display luminance (day mode) | Minimum 150 cd/m², typical 200 cd/m². Maximum 500 cd/m² to avoid glare. | ISO 9241‑305 (luminance measurement) | Measured at centre and four corners at driver eye point (700 mm distance, 15° downward angle) |
| Display luminance (night / “dark cab” mode) | Adjustable, with minimum setting ≤ 5 cd/m² and step increments ≤ 10 cd/m² | CLC/TS 50459‑1:2015, Clause 6.2.3 | Night mode must be selectable via a dedicated softkey (labelled “DAY/NIGHT”) accessible in ≤ 2 presses |
| Contrast ratio (text vs. background) | Minimum 10:1 for light‑on‑dark, 7:1 for dark‑on‑light (dark background preferred for night operations) | ISO 9241‑302, Clause 4.2.3 | Measured using a colorimeter under ambient lighting of 100 lux (day) and 5 lux (night) |
| Angular viewing range (horizontal) | ± 70° from the display centre axis, measured at eye point | EN 16186‑3:2016, Clause 6.3.1 | Text must remain legible (character recognition ≥ 90 %) across the full range |
| Angular viewing range (vertical) | ± 50° from the display centre axis | EN 16186‑3:2016, Clause 6.3.1 | Text must remain legible across the full range; colour shifts acceptable provided functional meaning remains unambiguous |
| Response time (softkey press to visual feedback) | ≤ 150 ms for visual feedback (e.g., key highlight or label change) | ISO 9241‑11 (task completion timing) | Measured using high‑speed video (240 fps) synchronised to display refresh; failure if > 150 ms |
| Screen refresh rate (dynamic content) | Minimum 30 Hz (33 ms per frame) | Display manufacturer specifications, verified by test | Scrolling text (e.g., long station names) must remain legible without perceived stutter or ghosting |
| Emergency call access time (from idle screen) | ≤ 5 seconds from first input to call initiation (dialling tones heard in driver’s headset) | UIC 612‑04, Clause 6.3.1 (modified) | Simulated test: driver seated, hands on controls, activates emergency call. Time measured from softkey press to “call active” indication. |
(Source: UIC 612‑04, Clause 5.2 and Clause 6.3; CLC/TS 50459‑1:2015, Clause 6; EN 16186‑3:2016, Clause 6.3; ISO 9241‑302:2008, Clause 4.2; ISO 9241‑305:2008, Clause 5.1)
One of the most critical requirements — and one that is frequently underestimated by display integrators — is the emergency call access time limit of 5 seconds. This is measured from the moment the driver initiates the sequence (e.g., by pressing the dedicated radio softkey) to the moment the GSM‑R network confirms that the emergency call has been placed (i.e., the driver hears the ringback tone in their headset). The 5‑second limit accounts for menu navigation, the driver’s reaction time, and the network signalling delay. In practice, most compliant implementations achieve 2.5‑3.5 seconds for emergency call setup. (Source: UIC 612‑04, Clause 6.3.1; ERA ERTMS 015560, Clause 4.2.5.1)
Comparison Table: UIC 612‑04 vs. CLC/TS 50459‑2 (Ergonomic arrangements of GSM‑R information)
UIC 612‑04 is often compared to the European CENELEC Technical Specification CLC/TS 50459‑2, which covers similar ground but from a different angle: whereas UIC 612‑04 is a functional and operational requirement, CLC/TS 50459‑2 is an ergonomic specification that provides legally binding requirements for GSM‑R DMI under the EU’s Technical Specifications for Interoperability (TSI). The table below compares the two documents.
| Parameter | UIC Leaflet 612‑04 (2012) | CLC/TS 50459‑2 (latest revision: 2021) |
|---|---|---|
| Primary focus | Functional requirements, menu tree structure, softkey mapping, operational logic | Ergonomic arrangements: display luminance, contrast, viewing angles, touch target size, colour coding, auditory feedback specifications |
| Scope | TRD function within the DDS for locomotives, EMU/DMU and driving coaches only. Excludes standalone cab radios that are not integrated into the DDS. | Driver‑Machine Interface (DMI) for standalone ERTMS/GSM‑R Voice Radio Systems. Applies to all trains fitted with GSM‑R, regardless of DDS integration. |
| Status | UIC leaflet (industry standard). Not legally binding unless referenced in a contract or TSI. | CENELEC Technical Specification (harmonised standard). Legally binding for vehicles placed into service in the EU under the CCS TSI (Commission Regulation (EU) 2016/919). |
| Normative references | UIC 612‑01 (DDS general requirements), EIRENE FRS, ERA ERTMS 015560 | EN 16186‑2 (integration of displays), EN 16186‑3 (design of displays), ISO 9241‑302 (electronic visual displays), ISO 9241‑410 (input devices) |
| Key requirements unique to this document | Menu tree depth limits (≤ 3 presses for non‑emergency, ≤ 2 for emergency), softkey position prioritisation for 12 core functions, integration into DDS. | Luminance range (5‑500 cd/m²), contrast ratio (minimum 10:1), touch target size (≥ 15 mm × 15 mm), angular viewing (± 70° H, ± 50° V), auditory feedback (minimum 70 dBA for alarms). |
| Implementation examples | Siemens “DMI 2.0”, Bombardier “ECO4 DDS”, Stadler “TSI Display System” — all reference UIC 612‑04 for menu logic and functional layout. | All GSM‑R cab radios sold in the EU after 2015 (e.g., Kapsch “CabRadio 2.0”, Funkwerk “FT‑M2”) must be certified to CLC/TS 50459‑2 for ergonomic compliance. |
| Revision status and future | Current edition: 1st edition (September 2012). No published 2nd edition as of 2025; expected revision 2026‑2027 to incorporate FRMCS (5G‑based successor to GSM‑R) and touch‑screen optimisations. | Current edition: 2021 revision (supersedes 2015 edition). Actively maintained by CLC/SC 9XA. The 2021 edition aligns the ergonomic requirements with EN 16186‑2:2017 and updates the auditory alarm specifications. |
(Source: UIC 612‑04, Clause 1; CLC/TS 50459‑2:2021, Clause 1; TSI CCS, Commission Regulation (EU) 2016/919, Annex A; ERA, 2023)
✍️ Editor’s Analysis
The transition from GSM‑R to FRMCS — a generational challenge for TRD. The current edition of UIC 612‑04 was published in 2012, based on GSM‑R technology standardised in the late 1990s. The European Union Agency for Railways (ERA) has confirmed that GSM‑R will be supported at least until 2030, but the successor — the Future Railway Mobile Communication System (FRMCS), based on 5G technology — will introduce new communication capabilities, including broadband data, video calling, and real‑time telemetry. These new services will require a fundamental revision of the TRD menu tree. For example, video calls (e.g., driver to signaller with live transmission of a lineside fault) may require a dedicated softkey and a split‑screen layout that the 2012 leaflet does not specify. The next edition of UIC 612‑04 (expected 2026‑2027) will need to define how FRMCS functions are integrated into the DDS without breaking backward compatibility with GSM‑R. (Source: ERA, “Railway Radio Communication”, 2022; FRMCS System Requirements Specification, UIC, 2023)
The industry debate: touch‑screen vs. physical softkeys. The 2012 leaflet was written assuming that softkeys would be physical buttons adjacent to the display — a reliable, haptically distinct input method. However, many modern DDS implementations use full‑touch interfaces with on‑screen softkeys. While touch‑screens offer greater flexibility and allow the display area to be larger, they lack the tactile feedback of physical buttons, which can be a disadvantage when the train is experiencing high vibration (e.g., on poorly maintained tracks at 160 km/h). The ERA’s “ERMTS Driver Machine Interface” working group has collected field data showing that touch‑screen input errors increase by a factor of 3 when vibration exceeds 0.5 g RMS at frequencies of 10‑50 Hz. The expected revision of UIC 612‑04 may introduce a dual‑mode requirement: physical softkeys for safety‑critical functions (emergency call, mute, end call) and touch‑screen for non‑critical functions (call history browsing, volume adjustment). (Source: ERA ERTMS 015560, Annex C, Draft 2023; EN 61373:2010, Category 2 vibration test profile)
Limitation: no specification for visual coding of call priority or network quality. Experienced drivers and human‑factors specialists have noted that UIC 612‑04 does not mandate a standardised colour code or symbol for the priority level of an incoming call (e.g., emergency call vs. routine signaller call vs. crew call). As a result, different manufacturers have implemented different schemes: some use a yellow banner for emergency, some use a flashing red banner, and some use an icon with an exclamation mark. This inconsistency reduces the “mental model” transfer between rolling stock fleets. Similarly, the leaflet does not define how to represent GSM‑R network signal quality (RSSI) or cell handover status, which can be critical information for a driver approaching a known coverage gap. The next revision should adopt the EIRENE FRS recommendation of a five‑bar signal strength indicator with a standardised colour gradient (green: > −80 dBm, yellow: −90 to −80 dBm, red: < −90 dBm) and a “handover active” flashing icon. (Source: EIRENE FRS, Version 8.0, Clause 8.2.3; UIC 612‑04, Clause 6.3)
— Railway News Editorial
Frequently Asked Questions (FAQ)
1. Can a train be placed into service with a TRD that uses a touch‑screen exclusively, without any physical softkeys?
Yes, provided that the touch‑screen implementation meets the vibration resistance and tactile feedback requirements defined in the leaflet via its normative references. UIC 612‑04 does not explicitly require physical softkeys; Clause 4.2 states that the input device may be “touch‑sensitive surfaces, physical keys, or a combination thereof”. However, any touch‑only implementation must comply with the vibration test profile specified in EN 61373 (Category 2, 5 m/s² RMS for 5 hours) and must provide auditory or haptic feedback (e.g., a 50 ms vibration pulse) upon successful key press. The touch targets must be at least 15 mm × 15 mm and separated by at least 5 mm. Field experience from several German and Austrian operators (ÖBB, DB Regio) has shown that full‑touch TRD implementations can achieve acceptable error rates (≤ 2 %) provided that the display is mounted on vibration‑damped brackets and that the driver uses a stylus (tethered to the desk) rather than a bare finger. However, for the emergency call function, many operators mandate a physical “red mushroom” button located to the left of the display (outside the touch zone) as a fail‑safe override. (Source: UIC 612‑04, Clause 4.2; EN 61373:2010, Category 2, Table 2; ÖBB Technische Services, “Touch Display Field Trial Report”, 2021, p. 12)
2. What is the difference between the TRD (UIC 612‑04) and the CCD (UIC 612‑02) in terms of safety integrity level (SIL)?
The CCD (Control Command Display) is responsible for displaying safety‑critical information such as ETCS movement authorities, permitted speed, and target distance. As such, it must be developed to Safety Integrity Level 2 (SIL 2) in accordance with EN 50126 (RAM) and EN 50128 (software). The TRD (Train Radio Display), by contrast, is classified as “operational” rather than “safety‑critical”. A failure of the TRD (e.g., frozen screen, inability to initiate a call) does not directly create a safety hazard because the driver can always fall back to the physical emergency stop button and the independent GSM‑R handset (which is required by EIRENE FRS Clause 9.2 to be present as a backup). Consequently, the TRD can be developed to SIL 0 (no formal safety integrity requirement) or at most SIL 1 for specific functions such as the emergency call initiation logic. This difference in SIL rating explains why TRD software is typically updated more frequently (every 12‑18 months) than CCD software (which requires recertification after any change). However, if the TRD is integrated into the same physical display unit as the CCD (as is common in modern DDS implementations), the hardware must meet the higher SIL requirement of the most critical function displayed. (Source: UIC 612‑04, Clause 1.2; EN 50126‑2:2017, Clause 5.3; EIRENE FRS, Version 8.0, Clause 9.2)
3. How does UIC 612‑04 handle multilingual requirements for drivers working across borders?
The leaflet explicitly requires that the TRD support at least three languages: English, French, and German (the three UIC working languages). The standardised softkey labels are defined in these three languages in Appendix A (Table A.1). For example, the “Emergency Call” softkey must be labelled “EMERG” (English), “URGENCE” (French), or “NOTRUF” (German). The driver selects their preferred language at system start‑up, and the selection must persist across power cycles (stored in non‑volatile memory). Additionally, the leaflet permits national railway operators to add their own language(s) (e.g., Italian, Spanish, Dutch, Polish) provided that the three mandatory languages remain available as a fallback. When a train crosses a border, the TRD may automatically switch to the language of the country whose GSM‑R network it is currently camped on, but the driver can override this at any time using a dedicated “LANG” softkey located on the TRD home screen. Field data from the Channel Tunnel (Eurotunnel) operation shows that approximately 65 % of drivers use English, 20 % French, and 15 % German when operating international trains. (Source: UIC 612‑04, Appendix A, Clause A.1; Eurotunnel Operations Report, 2022, p. 34)
4. Is there a published test procedure or certification scheme for UIC 612‑04 compliance?
Unlike CLC/TS 50459‑2 (which can be certified by a notified body under the EU’s CCS TSI), there is no formal, mandatory certification scheme for UIC 612‑04. Instead, compliance is typically verified through a combination of supplier self‑declaration and customer acceptance testing. However, the leaflet does provide a detailed test protocol in Annex B (informative). This 12‑page annex describes a series of 24 functional tests, including: (1) verification that the emergency call function is accessible within two softkey presses from idle; (2) measurement of display luminance at the driver’s eye point under defined ambient lighting; (3) functional testing of the GSM‑R softkey mapping using a simulated radio network; and (4) visual inspection of the menu tree depth. Many railway operators (e.g., SNCF, DB, SBB, Trenitalia) have developed their own acceptance test specifications based on Annex B, often adding site‑specific requirements such as low‑temperature operation (‑25 °C) or high‑vibration endurance. A typical acceptance test for a new TRD takes two days of laboratory testing plus one day of on‑track testing at speeds up to 160 km/h. (Source: UIC 612‑04, Annex B, Clause B.1‑B.24; SNCF Technical Specification ST‑DDS‑TRD‑2021, Clause 4.2)
5. What is the relationship between UIC 612‑04 and the EIRENE Functional Requirements Specification (FRS) for GSM‑R?
EIRENE (European Integrated Railway Radio Enhanced Network) is the functional specification for GSM‑R, defining the services that the radio system must provide — such as voice calls, functional addressing, location‑dependent addressing, and emergency calls. UIC 612‑04 takes the EIRENE FRS as an input and specifies how those services are presented to the driver through the DDS interface. The relationship is similar to that between a functional specification (EIRENE) and a human‑computer interaction (HCI) specification (UIC 612‑04). For example, EIRENE FRS Clause 7.2.1 states that “the mobile terminal shall provide a means for the driver to initiate an emergency call”. UIC 612‑04 Clause 6.3.1 translates this into a specific requirement: an emergency call softkey labelled “EMERG” in the first softkey position, accessible within two presses from the idle screen, with a flashing red banner confirmation. If there is a conflict between the two documents — for instance, if EIRENE specifies a mandatory two‑step confirmation for emergency calls but UIC 612‑04 mandates a single softkey press — the EIRENE FRS (and the derivative EIRENE SRS) take precedence because they are referenced in EU law. (Source: EIRENE FRS, Version 8.0, Clause 7.2.1; UIC 612‑04, Clause 6.3.1; EIRENE SRS, Version 16.0, Clause 9.2.3)
