CLC/TR 50542:2010

SLOVENSKI STANDARD
01-april-2010
äHOH]QLãNHQDSUDYH.RPXQLNDFLMVNDVUHGVWYDPHGVLJQDOQRYDUQRVWQRRSUHPRLQ
YPHVQLNLþORYHNVWURM00,
Railway applications - Communication means between safety equipment and man-
machine interfaces (MMI)
Applications ferroviaires - Moyens de communication entre l'équipement de sécurité et
l'interface homme-machine (IHM)
Ta slovenski standard je istoveten z: CLC/TR 50542:2010
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
45.020 Železniška tehnika na Railway engineering in
splošno general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

TECHNICAL REPORT
CLC/TR 50542
RAPPORT TECHNIQUE
February 2010
TECHNISCHER BERICHT
ICS 35.240.60, 45.020, 93.100
English version
Railway applications -
Communication means between safety equipment
and man-machine interfaces (MMI)

Applications ferroviaires -
Moyens de communication entre
l'équipement de sécurité et l'interface
homme-machine (IHM)
This Technical Report was approved by CENELEC on 2009-12-18.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus,
the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,
Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia,
Spain, Sweden, Switzerland and the United Kingdom.

CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung

Central Secretariat: Avenue Marnix 17, B - 1000 Brussels

© 2010 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. CLC/TR 50542:2010 E
Foreword
This Technical Report was prepared by the Technical Committee CENELEC TC 9X, Electrical and electronic
applications for railways.
It was circulated for voting in accordance with the Internal Regulations, Part 2, Subclause 11.4.3.3 (simple
majority).
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN and CENELEC shall not be held responsible for identifying any or all such patent rights.
This Technical Report has been prepared under a Mandate M/334 given to CENELEC by the European
Commission and the European Free Trade Association.
__________
- 3 - CLC/TR 50542:2010
Contents
1 Scope . 8
2 Normative references . 9
3 Terms and definitions . 10
4 Symbols and abbreviations . 12
5 Devices / modules of the systems . 13
6 DMI functions for ERTMS/ETCS . 13
6.1 Concepts . 13
6.2 Delays . 15
6.3 Object Controls analysis . 15
7 DMI Safety targets . 24
7.1 Difficulties to assign THR/SIL to ETCS Display display functions . 24
7.2 Safety approach for DMI and communication system . 27
8 Communication system requirements . 28
8.1 Strategy . 29
8.2 Connection to the DMI . 29
8.3 Object Control Layer . 30
8.4 Safety Layers . 30
8.5 Implicit Layer . 30
8.6 Objects Controls data format . 31
8.7 Safe Time Layer . 58
8.8 Safe Link Layer . 81
8.9 Implicit Layer . 101
8.10 Performances of HTI interface . 102
8.11 RAM requirements on HTI interface . 104
8.12 LCC requirements on HTI interface . 105
Annex A (informative) Actions . 106
Annex B (informative) Design rules . 113
B.1 List of design rules . 113
B.2 Function-specific rules . 114
Annex C (informative) Services provided by the Safe Time Layer . 115
Annex D (informative) Definition of notation . 116
D.1 State machine . 116
D.2 Sequence chart . 117
Annex E (informative) Safety Link Layer telegram sequences examples . 118
E.1 Telegram Sequences (SL 4 and SL 2 Point-to-Point Connections) . 118
E.2 Telegram Sequences (SL 0 Point-to-Point logical connections) . 124
Annex F (normative) CRC Generator Polynomial and Application Rules . 127
F.1 General . 127
Annex G (informative) Calculation of the CRC Length . 130
G.1 Safety target for the transmission (EN 50129) . 130
G.2 Calculation of the CRC length (SIL 2) . 133
Annex H (informative) Services provided by the Safe link layer . 135
Bibliography . 136

Figures
Figure 1 - Systems concerned by this document . 8
Figure 2— Terms and definitions . 10
Figure 3 — Fault tree model . 25
Figure 4 — Methodology for THR allocations. 27
Figure 5 — Communication system layers . 29
Figure 6 — Data encapsulation . 30
Figure 7 — Example for network architecture . 60
Figure 8 — Reference Time Transfert . 61
Figure 9 — Time stamp concepts . 62
Figure 10 — Architecture . 63
Figure 11 — Start up sequence . 64
Figure 12 — Time stamping . 69
Figure 13 — Reference clock transfer . 71
Figure 14 — Reference Clock state machine . 72
Figure 15 — Local Clock state machine . 74
Figure 16 — Logical Connection Master connection state machine . 76
Figure 17 — Logical Connection Slave state machine . 78
Figure 18 — Content of Safe Link Layer . 82
Figure 19 — General structure of a telegram . 82
Figure 20 — Supervision of Idle Telegrams . 92
Figure 21 — Example of the data flow for multicast messages . 98
Figure D.1 — State machine notations . 116
Figure D.2 — Sequence chart notation . 117
Figure E.1 — Telegram sequence to establish a SL 4 logical connection (connection set-up and
authentication) . 121
Figure E.2 — Telegram sequence of a faulty authentication due to an authentication telegram error 122
Figure E.3 — Telegram sequence to establish a SL 2 logical connection (connection set-up and
authentication) . 123
Figure E.4 — Telegram sequence for data exchange (SL 4 logical connection) . 124
Figure E.5 — Telegram sequence to establish a SL 0 logical connection (connection set-up) . 125
Figure E.6 — Telegram sequence for data exchange (SL 0 logical connection) . 126
Figure G.1 — Probability of undetected failures . 132
Tables
Table 1 — Object Controls from HS to DMI . 13
Table 2 — Object Controls from DMI to HS . 14
Table 3 — OC definitions, part 1 . 14
Table 4 — OC definitions, part 2 . 14
Table 5 — Delays from HS to DMI . 15
Table 6 — Delays from DMI to HS . 15
Table 7 — Exchanges from driver to HS . 16
Table 8 — Output exchanges from HS to driver . 18
Table 9 — Failure modes, part 1 . 21
Table 10 — Failure modes, part 2 . 22
Table 11 — Defence techniques, part 1 . 23

- 5 - CLC/TR 50542:2010
Table 12 — Defence techniques, part 2 . 24
Table 13 — Human behaviour . 26
Table 14 — THR allocation example . 28
Table 15 — Packet structure . 32
Table 16 — Message structure . 33
Table 17 — Indicator Request . 34
Table 18 — Button Request . 35
Table 19 — Text Message Request . 35
Table 20 — 8.6.5.4 Text Message Deletion . 36
Table 21 — Sound Request . 36
Table 22 — Data Entry Request . 37
Table 23 — Data Confirmation Request . 38
Table 24 — Dataview request . 39
Table 25 — Continuous Dataview Request. 40
Table 26 — Continuous Dataview Request for Announcement . 40
Table 27 — Button Event Report . 41
Table 28 — Text Ack . 41
Table 29 — Data Entry Reply . 42
Table 30 — Data Confirmation Reply . 42
Table 31 — Packets numbering . 43
Table 32 — Configuration Data . 65
Table 33 — Disconnect Reason . 65
Table 34 — Command number . 66
Table 35 — Application Data . 66
Table 36 — Sync and Reference Time . 67
Table 37 — Ready to Run . 67
Table 38 — Run . 68
Table 39 — Safe Time Layer Startup for multicast . 68
Table 40 — Constants for Safe Time Layer . 80
Table 41 — Detailed protocol structure of a telegram . 83
Table 42 — Structure of the Implicit Data . 85
Table 43 — Connect Request telegram . 86
Table 44 — Connect Confirm telegram . 87
Table 45 — Authentication telegram . 88
Table 46 — Authentication acknowledgement . 88
Table 47 — Disconnect telegram . 91
Table 48 — Idle telegram . 93
Table 49 — Data telegram Table . 93
Table 50 — Transition table, states . 94
Table 51 — Transition table, events . 94
Table 52 — Transition tables, actions (SL4 and SL2) . 95
Table 53 — Transitions (SL2 and SL4 connections) . 96
Table 54 — Transition table, actions (SL0) . 97
Table 55 — Transitions (SL0) . 97
Table 56 — Implicit Data format . 99

Table 57 — Multicast example . 100
Table 58 — Multicast telegram format . 100
Table 59 — Structure of the implicit data telegram . 101
Table 60 — List of services of lower layers services at HTI interface . 103
Table 61 — Performances of lower layers services at HTI interface . 104
Table A.1 . 106
Table A.2 — Actions for in-functions . 107
Table A.3 — Actions for out-functions . 110
Table B.1 — Design rules . 113
Table B.2 . 114
Table C.1 . 115
Table E.1 — Example of CRC computation for SL4 . 119
Table E.2 — Example of CRC computation for SL 2 . 120
Table G.1 . 130
Table H.1 — Service provided by the Safe Link Layer . 135

- 7 - CLC/TR 50542:2010
Introduction
The purpose of this Technical Report is to show how to harmonise the communication means between
onboard signalling safety systems and the driver-machine interface in the driver’s desk.
The need for this standardisation has grown out of several trends.
One trend is that the rolling stock is being computerised more and more, enabling sophisticated functions
within the rolling stock and various subsystems of the train.
1)
Further, the driver’s desk of such rolling stock is built around one or several computer screens . These
allow the driver to interact with the computerised rolling stock functions. The user interfaces are typically user
friendly, feature e.g. graphics and colours.
In case of degraded situation (screen failure) and with several screens available on the desk, it should be
possible to relocate important information to a screen that is still working. This improves operational
availability.
Another trend is the harmonisation of onboard signalling safety equipment. The ERTMS/ETCS as defined by
the directive 96/48/EC and the related Control-Command TSI defines a control-command signalling system
on European level.
For ERTMS/ETCS onboard, the driver-machine interface is also based on computerised screen(s).
The ERTMS/ETCS defines the concept of Specific Transmission Module STM, allowing the existing national
control-command systems to be modified into an STM. This allows integration between national control-
command systems and ERTMS/ETCS onboard equipment via a standardised interface (FFFIS STM).
Since desk space is a limited resource, the STM concept allows national onboard control-command systems
to use the driver machine interface resources of ERTMS/ETCS. This is one aspect of the integration of
national equipment with ERTMS/ETCS onboard.
Therefore the ERTMS/ETCS driver machine interface allows the driver to interact with any of the installed
STMs or/and ERTMS/ETCS onboard. The selection of the active system is a responsibility of ERTMS/ETCS.
A third trend is that a European market is opened for control-command equipment as well as rolling stock.
Traditionally, control-command systems were generally linked to a country, and rolling stock was equipped
with one or more national signalling safety system. This has effectively limited the rolling stock to operate
within a limited number of countries.
The ERTMS/ETCS, in combination with STMs makes available onboard signalling safety equipment that
enables cross-border traffic, freeing rolling stock from this barrier.
There are indeed other barriers hindering cross-border traffic, being operational, technical or administrative.
They are gradually being overcome. One example is the interoperable voice radio, EIRENE, based on
GSM-R.
———————
1)
In this Introduction the term “screen” is used in a popular sense, implying e.g. touch screen or other means of input from driver.

The combination of the above trends leads to the conclusion that during train operation, ERTMS/ETCS must
have access to one of the screens in the desk. Further, it is desirable to maintain the advantages of multi-
screen installations created by train system providers, allowing the ability to change screen for
ERTMS/ETCS in case of screen failure. Thus a certain level of integration and harmonised communication is
called for.
Another motivation for this Technical Report is related to Life Cycle Cost. The interface shown here helps
replacement of screen and desk equipment through the lifetime of the vehicle, whatever is the supplier.
1 Scope
This Technical Report defines, in accordance with the ERTMS/ETCS requirements:
a) for each DMI function to be exchanged to and from the driver, including ETCS, STM:
 performances needed;
 degraded modes recovering;
b) DMI Safety targets;
c) communication system requirements:
 real-time capability;
 performances (bandwidth, etc.);
 expansion capability;
 RAMS;
 applicable standards;
 degraded modes;
 degraded modes management;
 interface with other systems;
 LCC requirements.
Each item in the list above corresponds to one chapter of the present document.

Figure 1 - Systems concerned by this document

- 9 - CLC/TR 50542:2010
This Technical Report does not cover the following items:
 Train functions;
 STM “Separate DMI” as defined in document [1] regarding DMI equipment that is part of the STM itself;
 GSMR EIRENE functions;
 Ergonomics;
 Use of the ETCS DMI as a terminal server for maintenance purpose.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
96/48/EC, Council Directive 96/48/EC of 23 July 1996 on the interoperability of the trans-European high-
speed rail system
EN 50128, Railway applications - Communication, signalling and processing systems - Software for railway
control and protection systems
EN 50129, Railway applications - Communication, signalling and processing systems - Safety related
electronic systems for signalling
EN 50155, Railway applications - Electronic equipment used on rolling stock
EN 50159-1, Railway applications - Communication, signalling and processing systems - Part 1: Safety-
related communication in closed transmission systems
EN 50159-2:2001; Railway applications - Communication, signalling and processing systems - Part 2:
Safety-related communication in open transmission systems
CLC/TS 50459-2, Railway applications - Communication, signalling and processing systems - European Rail
Traffic Management System - Driver-Machine Interface - Part 2: Ergonomic arrangements of ERTMS/ETCS
information
CLC/TS 50459-6, Railway applications - Communication, signalling and processing systems - European Rail
Traffic Management System - Driver-Machine Interface - Part 6: Audible information

3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
Figure 2 is given to illustrate the relationship between some definitions.

Figure 2— Terms and definitions
3.1
Human-Machine Interface
functional interface between the DMI(s) and the driver
NOTE Information is carried through this interface in the form of visual (light), acoustic and tactile (driver’s pressing
of buttons). One HMI is associated with one or more DMIs.
3.2
Driver Machine Interface
equipment to support one HMI. It contains the hardware and software means to support HMI
3.3
Host System
equipment communicating with the Driver via DMI
3.4
host application
functional service allocated in a Host System
3.5
terminal system
system comprising the communication system and at least one DMI in a desk

- 11 - CLC/TR 50542:2010
3.6
hard key
physical key not part of the display area. This key can also have a text label or symbol
3.7
communication system
system connecting one or more Host System to one or more DMIs and/or to other HS
3.8
softkey
context-dependent key which consists of hard key with an associated label on the display area
3.9
in-function
exchange of information (data) from the driver to the onboard system
3.10
out-function
exchange of information (data) from the onboard system to the driver
3.11
button event
pressing or releasing a button
3.12
button
object shown to the driver through which the driver action is possible. It is composed of a label and the
associated sensitive area
NOTE The sensitive area of a button can be accessed via a touch screen area or via hardkey, depending on the
chosen technology.
3.13
dimmed
areas which appearance has been made less conspicuous than other areas
3.14
indicator
object with a label shown to the driver for which no driver action is possible
3.15
sensitive area
surface on which a driver can make a physical action to give input to the HS
3.16
Object Control
data exchanged between Host System and DMI
3.17
label
symbol or text indication on an indicator or a button

4 Symbols and abbreviations
ASIC Application Specific Integrated Circuit
CRC Cyclic Redundancy Code
DMI Driver Machine Interface
EMC Electromagnetic Compatibility
ERTMS European Rail Traffic Management System
ETCS European Train Control System
EVC European Vital Computer
FDL Field Data Link
FMEA Failure Mode and Effects Analysis
FRS Functional Requirements Specification
FFFIS Form Fits Functional Interface Specification
HMI Human-Machine Interface
HTI Host Terminal Interface
HW Hardware
IL Implicit Layer
LCC Life Cycle Cost
MTBF Mean Time Between Failures
OC Object Control
Profibus Process Field Bus
RAM(S) Reliability, Availability, Maintainability, (Safety)
SAP Service Access Point
SLL Safe Link Layer
STL Safe Time Layer
STM Specific Transmission Module
SW Software
- 13 - CLC/TR 50542:2010
5 Devices / modules of the systems
The different systems shown in Figure 1, are detailed hereafter:
1) the DMI(s). It can be constituted of (or it can be considered as the assembly of):
 input devices (from the driver to the system);
• button(s). The button(s) can be hardkeys or softkeys or an area on a touch screen, the so-
called "button event",
• etc.;
 output devices (from the system to the driver);
• visual devices,
• acoustic devices,
• etc.;
 a processing unit.
2) a communication system. It is constituted of:
 a hardware subsystem;
 a software subsystem.
 Each of those subsystems can be distributed on different devices.
3) the connected equipment (HS: for instance, EVC/STM system).
6 DMI functions for ERTMS/ETCS
6.1 Concepts
6.1.1 Object Controls
The study of exchanges between the driver and the ERMTS/ETCS system has led to define the following
generic Object Controls, that must be exchanged between Host System and DMI (see Table 1 to Table 4).
NOTE Those OCs must be usable by any HS connected to the communication system defined in this document.
Table 1 — Object Controls from HS to DMI
From Host System to DMI Name
Button request BR
Indicator request IR
Text message request TMR
Text message deletion TMD
Sound request SR
Data entry request DER
Data confirmation request DCR
Dataview request DR
Continuous dataview request CDR

Table 2 — Object Controls from DMI to HS
From DMI to Host System Name
Button event report BER
Ack ACK
Data entry reply DERy
Data confirmation reply DCRy
6.1.2 Objects Controls from HS to DMI
Table 3 gives precisions about the concept of OC from HS to DMI.
Table 3 — OC definitions, Part 1
Name Details
Button request HS request DMI to give or remove driver access to the related button.
Indicator request HS request DMI to display or remove the related indicator.
Text message request HS request DMI to display the related text. The request can consist of a reference to
the text, or it can include the text itself.
Text message deletion HS request DMI to remove a text message.
Sound request HS request DMI to play or stop playing a sound to the driver.
Data entry request HS request DMI to ask the driver to enter one or several data. The request can contain
one or more data values (e.g. default or current values), and a text identifying the data
for the driver.
Data confirmation request HS request DMI to ask the driver to confirm one or several data.
The request can contain one or more unconfirmed data values (e.g. recently given by
the driver), and a text identifying the data for the driver.
Dataview request HS request DMI to display or remove data to the driver.
Continuous dataview request HS request DMI to display or remove continuously changing data (e.g. speed, target
distance).
6.1.3 Objects Controls from DMI to HS
Table 4 gives precisions about the concept of OC from DMI to HS.
Table 4 — OC definitions, Part 2
Name Details
Button event report DMI report to HS button event .
Ack DMI report driver acknowledgement to HS.
Data entry reply DMI report to HS driver data entry.
Data confirmation reply DMI report to HS driver confirmation or rejection of data displayed.

- 15 - CLC/TR 50542:2010
6.2 Delays
For each OC, a maximum delay is defined and mandatory (Table 5 and Table 6). The following delays are
defined for the complete system (i.e. DMI + communication system):
Table 5 — Delays from HS to DMI
From Host System to DMI Name Delay
ms
Button request BR 500
Indicator request IR 500
Text message request TMR 1 000
Text message deletion TMD 500
Sound request SR 500
Data entry request DER 1 000
Data confirmation request DCR 1 000
Dataview request DR 1 000
Continuous dataview request CDR 500

Table 6 — Delays from DMI to HS
From DMI to Host System Name Delay
ms
Button event report BER 500
Ack ACK 500
Data entry reply DERy 1 000
Data confirmation reply DCRy 1 000

6.3 Object Controls analysis
6.3.1 Explanations
6.3.1.1 Object Controls and ERTMS/ETCS functions
The exchanges between the HS and the DMI have been analysed according to the documents [2], [3] and
CLC/TS 50459. Table 7 and Table 8 demonstrate that the OCs defined in 6.1.1 are covering all the needs for
all the functional exchanges between ERTMS/ETCS and the driver. Those Tables show one example of
implementation for each function, other solutions are allowed, but only by using OCs defined in 6.1.1.

6.3.1.1.1 Exchanges from driver to HS
Table 7 — Exchanges from driver to HS
ETCS Driver exchange SRS [2], STM [3], CLC/TS 50459 Associated OCs
Data entry request SRS 3.19, 4.7.2, 5.4 BR, BER
Train Data
Maximum Train Speed SRS 3.19, 4.7.2, 5.4, 5.14.2.2, 5.14.3.3 BR, BER, DER, DERy, DCR, DCRy
International Train category SRS 3.19, 4.7.2, 5.4, 5.14.2.2, 5.14.3.3 BR, BER, DER, DERy, DCR, DCRy
Train length SRS 3.19, 4.7.2, 5.4, 5.14.2.2, 5.14.3.3 BR, BER, DER, DERy, DCR, DCRy
Braking characteristics SRS 3.19, 4.7.2, 5.4, 5.14.2.2, 5.14.3.3 BR, BER, DER, DERy, DCR, DCRy
Loading gauge SRS 3.19, 4.7.2, 5.4, 5.14.2.2, 5.14.3.3 BR, BER, DER, DERy, DCR, DCRy
Axle load SRS 3.19, 4.7.2, 5.4, 5.14.2.2, 5.14.3.3 BR, BER, DER, DERy, DCR, DCRy
Power supply SRS 3.19, 4.7.2 BR, BER, DER, DERy, DCR, DCRy
Additional Data
Driver Identity number SRS 3.18.4.1, 4.7.2, 5.4 BR, BER, DER, DERy
Train Operational Identifier SRS 3.18.3.2.1, 3.18.4.5.1, 4.7.2, 5.4 BR, BER, DER, DERy
ERTMS/ETCS Level SRS 3.18.4.2, 4.7.2, 5.4, 5.10.2.9, BR, BER, DER, DERy
5.10.2.10
RBC Identity SRS 3.18.4.3.2, 4.7.2, 5.4 DER, DERy
RBC phone number SRS 3.18.4.3.2, 4.7.2, 5.4 DER, DERy
Track adhesion factor SRS 3.18.4.6, 4.7.2 BR, BER
Maximum Staff Responsible Speed SRS 4.4.11.1.5, 4.7.2, 5.8.3.5 BR, BER, DER, DERy
Staff Responsible distance SRS 4.4.11.1.5, 4.7.2, 5.8.3.5 BR, BER, DER, DERy
Additional STM data SRS 3.15.6.3, 4.4.6.1.9, 4.4.15.1.7, BR, BER, DER, DERy, DCR, DCRy
4.4.16, 4.4.17, 4.7.2, 5.4
STM selection SRS 3.18.4.2, 4.7.2, 5.4, 5.10.2 BR, BER, DER, DERy
Driver confirmation
Train Data Confirmation SRS 4.7.2, 5.4 DCR, DCRy
Confirm «Continue without radio SRS 5.4 DCR, DCRy
session»
Mode change request
Shunting Request SRS 4.4.8.1, 4.4.14.5, 4.7.2, 5.4, 5.6 BR, BER
Exit of Shunting request SRS 4.6.3, 4.7.2 BR, BER
Non-leading request SRS 4.4.15.3.2, 4.6.3, 4.7.2, BR, BER
5.5.12.3.4.1, 5.5.14.3.5
Exit of Non-leading request SRS 4.6.3, 4.7.2, 5.4, 5.12.3.4.2, BR, BER
5.14.2.4
- 17 - CLC/TR 50542:2010
Table 7 — Exchanges from driver to HS (continued)
ETCS Driver exchange SRS [2], STM [3], CLC/TS 50459 Associated OCs
Acknowledgement
Acknowledgement of train trip SRS 3.14.1.3, 4.4.13.1.4, 4.6.3, 5.11.3 ACK
Acknowledgement of Staff Responsible SRS 4.6.3, 4.7.2, 5.4 ACK
mode
Acknowledgement of On Sight mode SRS 4.6.3, 4.7.2, 5.4, 5.9.1.2, 5.9.2.3, 5.9.3 ACK
Acknowledgement of Unfitted mode SRS 4.6.3, 4.7.2, 5.4 ACK
Acknowledgement of shunting ordered by SRS 4.4.8.1.9, 4.6.3, 5.4, 5.7.1.4, 5.7.3.2 ACK
trackside
Acknowledgement of reversing mode SRS 4.6.3, 5.13 ACK
Acknowledgement of level transition to level SRS 4.7.2, 5.10.4 ACK
Acknowledgement of Plain Text Information SRS 3.12.3, 4.7.2 ACK
Acknowledgement of Fixed Text Information SRS 3.12.3, 4.7.2 ACK
Acknowledgement of release emergency SRS 3.14.1.8 ACK
brake
Acknowledgement of release service brake SRS 3.14.1.8 ACK
Other inputs
Confirmation of Train Integrity SRS 3.6.5.1.4, 3.6.5.2, 4.6.3, 4.7.2 BR, BER, DCR, DCRy
Track Ahead Free confirmation SRS 3.15.5.2, 4.11.1.9, 4.4.12.1.5, 4.7.2, BR, BER, DCR, DCRy
5.9.6.3.3
Override request SRS 4.4.11.1.8, 4.6.3, 4.7.2, 5.4.3.2, 5.6.4.1.3, BR, BER, DCR, DCRy
5.8.1, 5.8.2
Override route unsuitability SRS 3.12.2.5, 3.12.2.6, 4.7.2 BR, BER, DCR, DCRy
Start SRS 3.8.2.7, 4.4.11.1.6, 4.4.14.1, 4.6.3, 4.7.2, BR, BER
5.4.1.1, 5.4.3.2, 5.14.2.5
Selection of language SRS 3.12.3.3.2, 4.7.2 BR, BER, DER, DERy
Display request Supervision (including SRS 2.6.3.1.6, 4.4.8.1.11, 4.4.11.1.7, BR, BER
permitted speed and target distance, SR 4.4.12.1.4
speed and distance)
Display request geographical train position SRS 3.6.6.1, 4.7.2 BR, BER, TMR, TMD
DMI input for STM SRS 2.6.4.1, 3.15.6.3, 4.4.6.1.9, 4.4.15.1.7,
4.4.16, 4.4.17, 4.6.3, 4.7.2, 5.4
Packet STM-30: Driver language STM 7.5.1 BR, BER, DER, DERy
transmission
Packet STM-32: Button Request STM 7.5.2 BR
Packet STM-34: Button event report STM 7.5.3 BER
Packet STM-40: Acknowledgement reply STM 7.5.7 ACK

6.3.1.2 Output Exchanges from HS to driver
Table 8 — Output exchanges from HS to driver
ETCS Driver exchange SRS [2] ,STM [3], CLC/TS 50459 Associated OCs
Train Data
See input exchange BR, BER, DR
Additional Data See input exchange BR, BER, DR
Train status
Indication limit SRS 3.14.4.8 CDR
Warning limit SRS 3.14.4.5 CDR
Intervention limit SRS 3.14.4.6, 3.14.4.7 CDR
Train Speed SRS 2.6.3.1.6, 3.13.2.1, 4.4.8.1.10, 4.4.9.1.6, 4.4.10.1.4, CDR
4.4.11.1.7, 4.4.12.1.4, 4.4.15.1.6, 4.4.18.1.5, 4.7.2
Service Brake Indication SRS 3.13.4.6.5, 3.14.2.6, 3.14.3.4, 4.7.2 IR
Emergency Brake Indication SRS 3.13.4.7.4, 3.14.2.6, 3.14.3.4, 4.7.2 IR
Mode and level indication
ERTMS/ETCS Mode SRS 4.4.2.1, 4.7.2 IR
current ERTMS/ETCS level SRS 4.4.2.1, 4.7.2 IR
Ceiling Speed and Target Speed Monitoring
Permitted Speed SRS 2.6.3.1.6, 3.13.4.4.1, 3.13.7.3.6, 4.4.9.1.6, CDR
4.4.12.1.5, 4.4.18.1.5, 4.7.2
Target Speed SRS 3.13.2.2, 3.13.4.8.1, 4.4.9.1.6, 4.4.12.1.4, 4.7.2 CDR
Target Distance SRS 3.13.2.2, 3.13.4.8.1, 4.4.9.1.6, 4.4.12.1.4, CDR
4.4.18.1.5, 4.7.2
Release Speed SRS 3.13.7.3.5, 4.4.9.1.6, 4.7.2 CDR
Intervention Speed CLC/TS 50459-2 CDR
Supervised maximum speed SRS 2.6.3.1.6, 4.4.8.1.11, 4.4.11.1.7 CDR
Warning time to intervention CLC/TS 50459-2 CDR
Set Speed CLC/TS 50459-2 CDR
Warnings and Text Messages
Trip Alarm SRS 4.4.13.1.3, 4.7.2 IR, SR, CDR
Text message: Fixed text message SRS 3.12.3.1, 3.12.3.2, 3.12.3.3, 4.7.2, 4.8.3.1.1, TMR, TMD
4.10.1.3
Text message to be acknowledged: SRS 3.12.3.1, 3.12.3.2, 3.12.3.3, 4.7.2, 4.8.3.1.1, TMR, TMD
Fixed text messages 4.10.1.3
Plain Text Message SRS 3.12.3, 4.7.2, 4.8.3.1.1, 4.10.1.3 TMR, TMD

- 19 - CLC/TR 50542:2010
Table 8 — Output exchanges from HS to driver (continued)
ETCS Driver exchange SRS [2] ,STM [3], CLC/TS 50459 Associated OCs
Indications
Emergency stop message received SRS 3.10.2 IR
Local Time SRS 3.18.5.1.2 CDR
Override status SRS 4.4.11.1.7, 4.7.2 IR
SR mode proposed SRS 4.6.3, 4.7.2, 5.4 TMR,TMD
Slippery track selected SRS 3.18.4.6.2.3, 4.7.2 IR
Geographical train position SRS 3.6.6.1, 4.7.2 TMR, TMD
Isolation status SRS 4.4.2.1, 4.4.3.1.2, 4.7.2 IR
Track data and track condition SRS 3.12.1.1, 3.12.1.4, 3.12.1.5
Power control SRS 3.12.1, 4.7.2 IR
Stopping control SRS 3.12.1, 4.7.2 IR
Air tightness SRS 3.12.1, 4.7.2 IR
Balise transmission control SRS 3.12.1, 4.7.2 IR
Control radio transmission – Unchecked Area SRS 3.12.1, 4.7.2 “Radio hole control” IR
Brakes control SRS 3.12.1, 4.7.2 IR
Route suitability SRS 3.12.2.4 IR
TIU status CLC/TS 50459-2 IR
Planning Area CLC/TS 50459-2
Distance Scale(D1) CLC/TS 50459-2 CDR
Announcements area(D2/3/4) SRS 3.12.1.1, 3.12.1.4, 3.12.1.5, CLC/TS 50459-2 IR
Gradient Profile(D5) CLC/TS 50459-2 CDR
Speed Related Target(D6) CLC/TS 50459-2 CDR
Speed Profile(D7) CLC/TS 50459-2 CDR
Brake Curve Area Starting Point(D8) CLC/TS 50459-2 CDR
Confirmation
...