BS EN 61375-2-1:2012
$215.11
Electronic railway equipment. Train communication network (TCN) – Wire Train Bus (WTB)
Published By | Publication Date | Number of Pages |
BSI | 2012 | 390 |
This part of IEC 61375 applies to data communication in Open Trains, i.e. it covers data communication between consists of the said open trains and data communication within the consists of the said open trains.
The applicability of this standard to the train communication bus (WTB) allows for interoperability of individual consists within Open Trains in international traffic. The data communication bus inside consists (e.g. MVB) is given as recommended solution to cope with the said TCN. In any case, proof of compatibility between WTB and a proposed consist network will have to be brought by the supplier.
This standard may be additionally applicable to closed trains and multiple unit trains when so agreed between purchaser and supplier.
NOTE 1 For a definition of Open Trains, Multiple Unit Trains and Closed Trains, see Clause 3.
NOTE 2 Road vehicles such as buses and trolley buses are not considered in this standard.
PDF Catalog
PDF Pages | PDF Title |
---|---|
8 | English CONTENTS |
17 | INTRODUCTION Figures Figure 1 – Wire Train Bus |
18 | Figure 2 – Layering of the TCN |
19 | 1 Scope 2 Normative references |
20 | 3 Terms and definitions, abbreviations, conventions 3.1 Terms and definitions |
36 | 3.2 Abbreviations |
38 | 3.3 Conventions 3.3.1 Base of numeric values 3.3.2 Naming conventions 3.3.3 Time naming conventions |
39 | 3.3.4 Procedural interface conventions |
40 | Tables Table 1 – Template for the specification of an interface procedure |
41 | 3.3.5 Specification of transmitted data Table 2 – Example of message structure |
42 | Table 3 – Example of textual message form (corresponding to Table 2) |
43 | 3.3.6 State diagram conventions Figure 3 – State transition example Table 4 – State transitions table |
44 | 3.4 General considerations 3.4.1 Interface between equipment 3.4.2 Interface between consists 3.4.3 Real-Time Protocols Figure 4 – Interfaces between equipment Figure 5 – Interfaces between consists |
45 | 3.4.4 Network Management 3.4.5 Configurations Figure 6 – Train Bus and Consist network |
46 | 3.4.6 Structure of a standard device Figure 7 – TCN configurations |
47 | Figure 8 – TCN WTB device configuration options |
49 | 3.5 Conformance test Table 5 – Interoperability testing |
50 | 4 Physical layer 4.1 Topology 4.1.1 Bus sections 4.1.2 Couplers 4.1.3 Nodes 4.1.4 Consist orientation Figure 9 – Train Composition (two Intermediate Nodes shown) |
51 | 4.1.5 Consist specification (informal) Figure 10 – Vehicle measurement |
52 | 4.2 Medium specifications 4.2.1 Topology 4.2.2 Duplicated medium (option) Figure 11 – Connected nodes in regular operation |
53 | 4.2.3 Bus Configuration rules Figure 12 – Double-line attachment |
54 | 4.2.4 Cable specification |
55 | 4.2.5 Shielding concept |
56 | 4.2.6 Terminator Figure 13 – Grounded shield concept Figure 14 – Floating shield concept |
57 | 4.3 Medium attachment 4.3.1 Node connection points identification 4.3.2 Direct node attachment Figure 15 – Terminator Figure 16 – Direct node attachment (optional double-line) |
58 | 4.3.3 Indirect node attachment 4.3.4 Connector (optional) Figure 17 – Indirect attachment |
59 | 4.4 Node specifications 4.4.1 Node elements Figure 18 – WTB connector, front view Table 6 – WTB connector pin assignment |
60 | Figure 19 – Example of MAU Structure |
61 | 4.4.2 Node and switch settings 4.4.3 Duplicated Line Units (option) |
62 | 4.5 Line Unit specifications 4.5.1 Galvanic separation 4.5.2 Insertion losses of a Line Unit Figure 20 – Node with redundant Line Units |
63 | 4.5.3 Switches specifications 4.5.4 Shield connection to a Line Unit Figure 21 – Attenuation measurement |
64 | 4.5.5 Fritting (option) Figure 22 – Shield grounding in the Line Unit Figure 23 – Fritting source and load |
65 | 4.6 Transceiver specifications 4.6.1 Conventions 4.6.2 Transmitter |
66 | Figure 24 – Transmitter fixtures |
67 | Figure 25 – Pulse wave form at transmitter |
68 | 4.6.3 Receiver specifications Figure 26 – Signal and idling at transmitter |
69 | Figure 27 – Receiver signal envelope |
70 | 4.7 Medium-dependent signalling 4.7.1 Frame encoding and decoding Figure 28 – Receiver edge distortion |
71 | Figure 29 – Idealised frame on the line (16 bit Preamble shown) Figure 30 – Bit encoding Figure 31 – Preamble |
72 | Figure 32 – End Delimiter |
73 | 4.7.2 Duplicated line handling (option) Figure 33 – Valid frame, RxS, CS and SQE signals Figure 34 – Garbled frame, RxS, CS, SQE signals |
74 | Figure 35 – Redundant Lines (as seen at a receiver) |
75 | 4.7.3 Line Unit interface Figure 36 – Line_Disturbance signals |
76 | 5 Link Layer Control 5.1 Addressing Table 7 – Signals of the Line Unit Interface |
77 | 5.2 Frames and telegrams 5.2.1 Frame_Data format Figure 37 – HDLC Frame structure |
78 | 5.2.2 Telegram timing Figure 38 – Telegram timing |
79 | Figure 39 – Example of Interframe spacing |
80 | 5.2.3 Elements of the HDLC Frame Figure 40 – Frame spacing measured at the master side Figure 41 – Frame spacing at the slave |
81 | 5.2.4 Link Control Field Figure 42 – HDLC Data format Figure 43 – Format of HDLC Data |
82 | Table 8 – Link Control encoding |
84 | 5.2.5 Handling of ‘Attention’, ‘Change’ and ‘Inhibit’ 5.2.6 Size, FCS and protocol errors 5.3 Telegram formats and protocols 5.3.1 Link Data field |
85 | 5.3.2 Process Data Figure 44 – Process Data telegram |
86 | Figure 45 – Format of Process Data Request |
87 | 5.3.3 Message Data Figure 46 – Format of Process Data Response Figure 47 – Message Data telegram Figure 48 – Format of Message Data Request |
88 | 5.3.4 Supervisory Data Figure 49 – Format of Message Data Response Figure 50 – Supervisory telegram |
89 | 5.3.5 Detection telegram Figure 51 – Detection telegram |
90 | Figure 52 – Format of Detect Request Figure 53 – Format of Detect Response |
91 | 5.3.6 Presence telegram Figure 54 – Presence telegram Figure 55 – Format of Presence Request |
92 | 5.3.7 Status telegram Figure 56 – Format of Presence Response Figure 57 – Status telegram |
93 | Figure 58 – Format of Status Request |
94 | 5.3.8 Set to Intermediate telegram Figure 59 – Format of Status Response Figure 60 – Set-to-Intermediate telegram Figure 61 – Format of SetInt Request |
95 | 5.3.9 Naming telegram Figure 62 – Format of SetInt Response Figure 63 – Naming telegram |
96 | Figure 64 – Format of Naming Request Figure 65 – Format of Naming Response |
97 | 5.3.10 Unname telegram 5.3.11 Set to End telegram Figure 66 – Unnaming telegram Figure 67 – Format of Unname Request Figure 68 – Set to End telegram |
98 | Figure 69 – Format of SetEnd Request Figure 70 – Format of SetEnd Response |
99 | 5.3.12 Topography telegram Figure 71 – Topography telegram Figure 72 – Format of Topography Request |
100 | Figure 73 – Format of Topography Response |
101 | 5.4 Medium allocation 5.4.1 Organisation Figure 74 – Structure of the Basic Period |
102 | 5.4.2 Periodic Phase |
103 | 5.4.3 Sporadic phase 5.5 Inauguration 5.5.1 General |
104 | Figure 75 – Node position numbering |
105 | 5.5.2 Descriptors Figure 76 – Format of Node Descriptor |
106 | Figure 77 – Format of Node Report Figure 78 – Format of User Report |
107 | Figure 79 – Format of Composition Strength |
108 | Figure 80 – Master_Report Figure 81 – Format of Topo Counter |
109 | 5.5.3 Detection of other compositions (informal) Figure 82 – Format of Master Topo |
111 | Figure 83 – Timing Diagram of detection protocol |
112 | 5.5.4 State diagrams of the inauguration Figure 84 – Major node states and application settings |
113 | Figure 85 – Node processes (End Setting) |
114 | Table 9 – NodeControl data structure |
115 | Table 10 – MyStatus data structure |
116 | Table 11 – Shared Variables of a node Table 12 – Variables of Main Process |
117 | Table 13 – Lists of Main Process |
119 | Figure 86 – AUXILIARY_PROCESS states |
120 | Figure 87 – NAMING_RESPONSE macro |
121 | Figure 88 – States of MAIN PROCESS |
122 | Table 14 – ‘START_NODE’ Table 15 – ‘MASTER STATES’ |
123 | Table 16 – ‘SLAVE STATES’ |
124 | Figure 89 – Macro ‘START_NODE’ |
126 | Figure 90 – Procedure REQUEST_RESPONSE |
127 | Figure 91 – Procedures ‘SET_TO_INT’ and ‘SET_TO_END’ |
128 | Figure 92 – Macro ‘INIT_MASTER’ |
129 | Figure 93 – Macro ‘NAMING_MASTER’ |
130 | Figure 94 – Macro ASK_END |
133 | Figure 95 – Procedure NAME_ONE |
135 | Figure 96 – Macro TEACHING_MASTER |
136 | Figure 97 – Macro ‘UNNAMING_MASTER’ |
138 | Figure 98 – Macro ‘REGULAR_MASTER’ |
139 | Figure 99 – Macro CHECK_DESC |
141 | Figure 100 – Macro PERIODIC_POLL |
142 | Figure 101 – Macro MESSAGE_POLL |
144 | Figure 102 – States ‘UNNAMED_SLAVE’ |
146 | Figure 103 – States ‘NAMED_SLAVE’ |
148 | Figure 104 – Macro ‘LEARNING_SLAVE’ |
150 | Figure 105 – Macro ‘REGULAR_SLAVE’ |
151 | Table 17 – Time constant values |
152 | 5.6 Link layer interface 5.6.1 Link layer layering Figure 106 – Link layer layering |
153 | 5.6.2 Link Process_Data_Interface |
154 | 5.6.3 Link Message_Data_Interface 5.6.4 Link management interface |
165 | 6 Real-Time protocols 6.1 General 6.1.1 Contents of this clause Figure 107 – Structure of the Train Communication Network |
166 | 6.1.2 Structure of this clause Figure 108 – Real-Time Protocols layering |
167 | 6.2 Variables – Services and Protocols 6.2.1 General 6.2.2 Link layer Interface for Process_Data |
170 | Figure 109 – LPI primitives exchange Table 18 – LPI primitives |
173 | 6.2.3 Application interface for Process_Variables |
175 | Figure 110 – Check_Variable |
177 | Table 19 – Var_Size and Var_Type encoding in a PV_Name |
179 | Figure 111 – Individual access |
183 | Figure 112 – Set access |
186 | Figure 113 – Cluster access |
188 | 6.3 Messages Services and Protocols 6.3.1 General 6.3.2 Reference station Figure 114 – Terminal station |
189 | Figure 115 – Router station between WTB and MVB |
190 | Figure 116 – Gateway station between WTB and Consist network |
191 | 6.3.3 Message packets handling |
192 | Figure 117 – Packet format |
193 | 6.3.4 Message Link layer |
194 | Figure 118 – Link layer data transmission |
195 | Figure 119 – Link_Message_Data_Interface (LMI) |
196 | Figure 120 – Example of MVB Message_Data frame |
197 | Figure 121 – Example of WTB Message_Data frame |
198 | Figure 122 – LMI primitives |
199 | Table 20 – LMI primitives |
203 | 6.3.5 Message Network Layer |
204 | Figure 123 – Network layer on a Node |
207 | Figure 124 – Encoding of the Network_Address |
209 | Figure 125 – Building of the addresses in an outbound packet |
210 | Figure 126 – Network address encoding on the train bus |
211 | Table 21 – Routing situations |
213 | Table 22 – Routing of packets coming from the transport layer |
214 | Table 23 – Routing of packets coming from a consist network |
215 | 6.3.6 Message transport layer Table 24 – Routing of packets coming from the train bus |
217 | Figure 127 – Transport packet exchange |
219 | Figure 128 – Packet formats (transport layer body) |
220 | Table 25 – Message Transport Control encoding |
223 | Table 26 – Connect_Request Table 27 – Connect_Confirm |
224 | Table 28 – Disconnect_Request Table 29 – Disconnect_Confirm Table 30 – Data_Packet |
225 | Table 31 – Ack_Packet Table 32 – Nak_Packet Table 33 – Broadcast_Connect (BC1, BC2, BC3) |
226 | Table 34 – Broadcast_Data Table 35 – Broadcast_Repeat |
227 | Table 36 – Broadcast_Stop (BSC, BSO) Table 37 – MTP states |
228 | Figure 129 – State transition diagram of the MTP |
229 | Table 38 – MTP incoming events Table 39 – MTP outgoing events |
230 | Table 40 – MTP control parameters Table 41 – MTP auxiliary variables |
231 | Figure 130 – Time-out SEND_TMO |
232 | Figure 131 – Time-out ALIVE_TMO Table 42 – MTP time-outs (worst case) Table 43 – Implicit actions |
233 | Table 44 – Compound actions |
234 | Table 45 – Producer states and transitions |
237 | Table 46 – Consumer states and transitions |
240 | Figure 132 – Transport interface |
241 | Table 47 – TMI primitives |
246 | 6.3.7 Multicast Transport Protocol (option) |
247 | Figure 133 – Multicast message with no retransmission |
248 | Figure 134 – Short multicast message with no BD packets and no loss |
249 | Figure 135 – Exchange with lost packets |
251 | Figure 136 – Packet formats |
252 | Figure 137 – Protocol machine states Table 48 – States of the MCP machine |
253 | Table 49 – Incoming Events Table 50 – Outgoing Events |
254 | Table 51 – Control fields in packets |
255 | Table 52 – Auxiliary variables |
256 | Table 53 – MCP constants Table 54 – MCP time-outs |
257 | Table 55 – MCP Compound actions |
258 | Table 56 – Filtering of BR packets |
259 | Table 57 – MCP Producer state event table |
261 | Table 58 – MCP Consumer state event table |
262 | 6.3.8 Message session layer |
263 | Figure 138 – Session layer transfer |
264 | 6.3.9 Message Presentation Layer 6.3.10 Message Application layer Figure 139 – Session_Header in Call_Message (of type Am_Result) |
265 | Figure 140 – Application_Messages_Interface |
266 | Table 59 – AMI primitives |
268 | Table 60 – Address constants |
269 | Figure 141 – Encoding of AM_ADDRESS |
271 | Table 61 – System Address and User Address |
285 | 6.4 Presentation and encoding of transmitted and stored data 6.4.1 Purpose |
286 | 6.4.2 Data ordering |
287 | 6.4.3 Notation for the primitive types |
294 | 6.4.4 Structured types |
303 | 6.4.5 Alignment 6.4.6 Notation for special types |
305 | 7 Application Layer 7.1 Process Data Marshalling 7.1.1 Marshalling Types 7.1.2 Marshalling Modes Figure 142 – Process Data Marshalling |
306 | 7.1.3 Data Paths in PDM Figure 143 – PDM Data Paths |
307 | 7.1.4 PDM Operation |
308 | 7.1.5 PDM Functions Figure 144 – PDM Operation Figure 145 – PDM Invalidate Variable or Function result |
310 | 7.2 WTB Line Fault Location Detection Figure 146 – PDM Operation Figure 147 – PDM Validty check |
311 | 7.2.1 Architecture Figure 148 – LFLD Architecture |
312 | 7.2.2 Protocol Overview |
313 | 7.2.3 LFLD Sequence Figure 149 – LFLD sequence |
315 | 7.2.4 End Node State Machine (Testing Node) 7.2.5 Intermediate Node State Machine (Segmenting Node) 7.2.6 Disturbed Line selection 7.2.7 Location Detection Figure 150 – End node state machine |
316 | Figure 151 – LFLD process, SN at node 63 Figure 152 – LFLD process, SN at node 1 |
317 | 8 Train Network Management 8.1 General 8.1.1 Contents of this clause Figure 153 – LFLD process, SN at node 1, attachment in direction 1 |
318 | 8.1.2 Structure of this clause 8.2 Manager, Agents and interfaces 8.2.1 Manager and Agent 8.2.2 Management messages protocol |
319 | 8.2.3 Interfaces Figure 154 – Management messages |
320 | Figure 155 – Agent Interface on a (gateway) Station |
321 | 8.3 Managed objects 8.3.1 Object Attributes 8.3.2 Station objects |
322 | Figure 156 – Station_Status |
324 | 8.3.3 WTB link objects |
325 | 8.3.4 Variable objects |
327 | 8.3.5 Messenger objects |
328 | 8.3.6 Domain objects 8.3.7 Task objects |
329 | 8.3.8 Clock object 8.3.9 Journal object |
330 | 8.3.10 Equipment object 8.4 Services and management messages 8.4.1 Notation for all management messages |
335 | 8.4.2 Station services |
342 | 8.4.3 WTB link services |
354 | 8.4.4 Variables services |
364 | 8.4.5 Messages services |
373 | 8.4.6 Domain services |
378 | 8.4.7 Task services |
380 | 8.4.8 Clock services |
381 | 8.4.9 Journal Service |
383 | 8.4.10 Equipment Service |
384 | 8.5 Interface Procedures 8.5.1 Manager interface (MGI) |
385 | 8.5.2 Agent interface |
388 | Bibliography |