Railway applications - Communication means between safety equipment and man-machine interfaces (MMI)

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.

Applications ferroviaires - Moyens de communication entre l'équipement de sécurité et l'interface homme-machine (IHM)

Železniške naprave - Komunikacijska sredstva med signalnovarnostno opremo in vmesniki človek-stroj (MMI)

To tehnično poročilo v skladu z zahtevami ERTMS/ETCS določa: a) za vsako funkcijo DMI, ki poteka do in od voznika, vključno z ETCS, STM:   potrebno delovanje; popravilo okvar; b) varnostne cilje DMI; c) zahteve za komunikacijski sistem: zmogljivost v realnem času; delovanje (pasovna širina, itd.); širitvena zmogljivost; RAMS; veljavni standardi; okvare; upravljanje z okvarami; vmesniško povezovanje z drugimi sistemi; zahteve za LCC. Vsaka postavka na zgornjem seznamu ustreza enemu poglavju v pričujočem dokumentu.

General Information

Status
Withdrawn
Publication Date
04-Feb-2010
Current Stage
9960 - Withdrawal effective - Withdrawal
Completion Date
17-Oct-2014

Relations

Buy Standard

Technical report
TP CLC/TR 50542:2010
English language
136 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-april-2010
äHOH]QLãNHQDSUDYH.RPXQLNDFLMVNDVUHGVWYDPHGVLJQDOQRYDUQRVWQRRSUHPRLQ
YPHVQLNLþORYHNVWURM 00,
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 —
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.