๐Ÿ”ฅ๐Ÿ”ฅ Donโ€™t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

๐Ÿ”
BS EN IEC 61375-2-6:2018

BS EN IEC 61375-2-6:2018

$215.11

Electronic railway equipment. Train communication network (TCN) – On-board to ground communication

Published By Publication Date Number of Pages
BSI 2018 124
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. Weโ€™re here to assist you 24/7.
Email:[email protected]

This part of IEC 61375 establishes the specification for the communication between the on-board subsystems and the ground subsystems.

The communication system, interfaces and protocols are specified as a mobile communication function, using any available wireless technology.

This document provides requirements in order to:

  1. select the wireless network on the basis of QoS parameters requested by the application;

  2. allow TCMS and/or OMTS applications, installed on-board and communicating on the on-board communication network, to have a remote access to applications running on ground installations;

  3. allow applications running on ground installations to have a remote access to the TCMS and/or OMTS applications installed on-board.

This document specifies further requirements which allow the applications running on-board and the applications running on ground to connect each other applying the virtual/functional addressing mechanism specified by IEC 61375-2-3 and exchanging application data sets produced or consumed by the on-board functions implemented in the devices attached to the TCN network.

Furthermore, this document covers the security requirements in order to grant the access only to authenticated and authorised applications and to allow encryption of exchanged data.

The communication of safety related data between on-board applications and ground applications are out of the scope of this International Standard as well as Internet connectivity service for passengers.

PDF Catalog

PDF Pages PDF Title
2 undefined
5 Annex ZA(normative)Normative references to international publicationswith their corresponding European publications
7 Annex ZZ(informative)Relationship between this European standard and the essential requirements of EU Directive 2016/797/EU [2016 OJ L138] aimed to be covered
9 English
CONTENTS
15 FOREWORD
17 INTRODUCTION
18 1 Scope
2 Normative references
19 3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
26 3.2 Symbols and abbreviated terms
28 3.3 State diagram conventions
4 Board to Ground Communication system architecture
4.1 General
4.2 Requirements
29 Tables
Table 1 โ€“ Board to ground requirements
30 4.3 Mobile communication network architecture
4.3.1 General
4.3.2 On-board network interface
Figures
Figure 1 โ€“ Train on-board communication system (example)
31 4.4 System breakdown structure
4.4.1 General
Figure 2 โ€“ Ground communication system (example)
32 4.4.2 System breakdown structure at board-to-ground system level
4.4.3 System breakdown structure at MCG sub-system level
4.4.4 System breakdown structure at GCG sub-system level
4.5 Functional breakdown structure
Table 2 โ€“ Board-to-ground system breakdown
Table 3 โ€“ MCG sub-system breakdown
Table 4 โ€“ GCG sub-system breakdown
33 4.6 Mobile Communication Gateway
4.6.1 Architecture
Table 5 โ€“ An example of the MCG function breakdown
Table 6 โ€“ An example of the GCG function breakdown
34 Figure 3 โ€“ Option 1: End device board to ground communication via MCG
35 4.6.2 Mobile communication gateway
Figure 4 โ€“ Option 2: End Device board to ground communicationvia dedicated interface
36 Figure 5 โ€“ MCG abstract model block diagram
Figure 6 โ€“ MCG configured as ALG
37 4.7 Mobile communication redundancy
4.7.1 General
Figure 7 โ€“ Architectural example of redundant Board to Ground communication
38 4.7.2 Full performance redundancy
4.7.3 Reduced performance redundancy
4.8 Train composition changes
Table 7 โ€“ Device โ€“ status of implementation of the TIS
Table 8 โ€“ Composition โ€“ status of implementation of the TIS
39 4.9 Security
4.9.1 Security zones
40 4.9.2 Security measures
Figure 8 โ€“ Security zones (simplified)
41 Table 9 โ€“ Security measures
42 4.9.3 Authentication authorization accounting model
43 Figure 9 โ€“ Authentication, authorization and accounting model
44 4.9.4 Network and MCG classification
Table 10 โ€“ MCG categories
45 Figure 10 โ€“ MCG connecting open and closed transmission systems
Table 11 โ€“ Security requirements
46 5 Communication framework
5.1 General
5.2 MCG broker service architecture
47 5.3 Addressing concept
5.3.1 Use cases
Figure 11 โ€“ MCG broker service architecture
48 5.3.2 Consist and train Identification
5.3.3 T2G Network Borders
5.3.4 T2G basic minimum network
Figure 12 โ€“ Minimum Train to Ground Network Setup
49 5.3.5 T2G addressing
Figure 13 โ€“ A train consisting of four vehicles
51 5.3.6 HTTP-URI
Table 12 โ€“ TCN-URI global DNS zone
52 5.4 Data classes for T2G communication
5.4.1 General
5.4.2 Communication channel establishment
5.4.3 Message data
53 5.4.4 Process data
Table 13 โ€“ Recommended service parameters for message data
54 5.4.5 Stream Data
5.4.6 Best effort data
Table 14 โ€“ Recommended service parameters for process data
Table 15 โ€“ Recommended service parameters for stream data
55 5.5 Communication protocol
5.5.1 General
5.5.2 HTTP(S)
Table 16 โ€“ Recommended service parameters for best effort data
56 Figure 14 โ€“ Communication stacks
Figure 15 โ€“ HTTP(S) MD communication pattern
57 5.5.3 MQTT (Option)
Figure 16 โ€“ HTTP(S) request/event
Figure 17 โ€“ HTTP(S) response
Table 17 โ€“ HTTP(S) parameters request/response pattern
58 5.6 Communication services
5.6.1 General
5.6.2 Message data communication service
59 Figure 18 โ€“ Message Data exchange (example)
60 Figure 19 โ€“ Message Data telegram structure
Table 18 โ€“ General MD Header
61 Table 19 โ€“ General MD Body
Table 20 โ€“ MD Checksum
Table 21 โ€“ Message types
62 5.6.3 File transfer communication service
Table 22 โ€“ Message representation
Table 23 โ€“ File transfer terminology
63 Figure 20 โ€“ File upload example
64 Table 24 โ€“ ComID 202: MD header telegram values
Table 25 โ€“ ComID 202: MD body telegram values
65 Table 26 โ€“ ComID 202: MD body: mdPayload object
Table 27 โ€“ ComID 203: MD header telegram values
Table 28 โ€“ ComID 203: MD body telegram values
66 Table 29 โ€“ ComID 203: MD body: mdPayload object
Table 30 โ€“ ComID 206: MD header telegram values
Table 31 โ€“ ComID 206: MD body telegram values
67 Table 32 โ€“ ComID 206: MD body: mdPayload object
Table 33 โ€“ ComID 207: MD header telegram values
Table 34 โ€“ ComID 207: MD body telegram values
68 Figure 21 โ€“ Error case: No ComID 203 received
Table 35 โ€“ ComID 207: MD body: mdPayload object
69 Figure 22 โ€“ Error case: no ComID 206 received, no file uploaded to the wayside
70 Figure 23 โ€“ Error Case: No ComID 206 received, file uploaded to the wayside
71 Figure 24 โ€“ Error Case: No ComID 207 received
72 Figure 25 โ€“ File download example
73 Table 36 โ€“ ComID 208: MD header telegram values
Table 37 โ€“ ComID 208: MD Body telegram values
74 Table 38 โ€“ ComID 208: MD Body: mdPayload object
Table 39 โ€“ ComID 209: MD header telegram values
75 Table 40 โ€“ ComID 209: MD Body telegram values
Table 41 โ€“ ComID 209: MD Body: mdPayload object
Table 42 โ€“ ComID 210: MD header telegram values
76 Table 43 โ€“ ComID 210: MD Body telegram values
Table 44 โ€“ ComID 210: MD Body: mdPayload object
Table 45 โ€“ ComID 211: MD header telegram values
Table 46 โ€“ ComID 211: MD Body telegram values
77 Table 47 โ€“ ComID 211: MD Body: mdPayload object
78 Figure 26 โ€“ Error case: no ComID 209 received
79 Figure 27 โ€“ Error case: no ComID 211 received
80 Figure 28 โ€“ Error case: no ComID 210 received
81 Table 48 โ€“ Main parts of dlTarget URI
Table 49 โ€“ Main parts of host element
82 Table 50 โ€“ Valid โ€œdeviceโ€ label values
Table 51 โ€“ Valid โ€œvehicleโ€ label values
Table 52 โ€“ Valid โ€œconsistโ€ label values
83 6 Services and interfaces (MCG)
6.1 Overview
6.1.1 MCG system service architecture
Table 53 โ€“ Valid โ€œclosed trainโ€ label values
Table 54 โ€“ Valid โ€œtrainโ€ label values
Table 55 โ€“ Exemplary dlTarget values
84 6.1.2 MCG / GCG system service interfaces
Figure 29 โ€“ Service architecture
85 6.1.3 MCG / GCG communication relationship
6.2 Service provisioning
Figure 30 โ€“ Service interfaces
86 6.3 MCG / GCG system service description
6.3.1 Communication Services
87 Figure 31 โ€“ Procedure to establish the radio link from MCG
Figure 32 โ€“ Procedure to establish the radio link from GCG
88 Figure 33 โ€“ Procedure to update the ground DNS server
Table 56 โ€“ ComID 240: Capability message
89 6.3.2 Train Location Service (Option)
Table 57 โ€“ ComID 240: MD event body telegram values
Table 58 โ€“ ComID 240: MD event body: mdPayload object
90 Figure 34 โ€“ Example architecture to provide the train location
91 Figure 35 โ€“ Example procedure to notify about current train location
92 Table 59 โ€“ ComID 230: MD request header telegram values
Table 60 โ€“ ComID 230: MD request body telegram values
Table 61 โ€“ ComID 230: MD request body: mdPayload object
93 Table 62 โ€“ ComID 230: MD reply header telegram values
Table 63 โ€“ ComID 230: MD reply body telegram values
Table 64 โ€“ ComID 230/232: MD reply/notification body: mdPayload object
94 Table 65 โ€“ Example of latitude/longitude with proposed fixed point notation
Table 66 โ€“ ComID 232: MD header telegram values
Table 67 โ€“ ComID 232: MD Body telegram values
95 6.3.3 Train Information Service
Figure 36 โ€“ Example architecture to notify about train information
96 Figure 37 โ€“ Example procedure to notify about train information
97 Table 68 โ€“ ComID 234: MD request header telegram values
Table 69 โ€“ ComID 234: MD request body telegram values
Table 70 โ€“ ComID 234: MD request body: mdPayload object
Table 71 โ€“ ComID 234: MD reply header telegram values
98 Table 72 โ€“ ComID 234: MD reply body telegram values
Table 73 โ€“ ComID 234: MD reply body: mdPayload object
99 6.3.4 MCG Network Selector Service
Table 74 โ€“ ComID 236: MD header telegram values
Table 75 โ€“ ComID 236: MD Body telegram values
100 Figure 38 โ€“ Illustration of network selector
101 6.3.5 Train telemetry service (Option)
Figure 39 โ€“ Architecture to provide telemetry data
102 Figure 40 โ€“ Procedure to notify about current train location
103 Table 76 โ€“ ComID 240: MD request header telegram values
Table 77 โ€“ ComID 240: MD request Body telegram values
104 Table 78 โ€“ ComID 240: MD reply header telegram values
Table 79 โ€“ ComID 240: MD reply body telegram values
Table 80 โ€“ ComID 240: MD reply body: mdPayload object
105 Table 81 โ€“ ComID 242: MD request header telegram values
Table 82 โ€“ ComID 242: MD request Body telegram values
106 Table 83 โ€“ ComID 242: MD request body: mdPayload object
Table 84 โ€“ ComID 242: MD reply header telegram values
107 Table 85 โ€“ ComID 242: MD reply body telegram values
Table 86 โ€“ ComID 242: MD reply body: mdPayload object
108 Table 87 โ€“ ComID 243: MD request header telegram values
Table 88 โ€“ ComID 243: MD request Body telegram values
Table 89 โ€“ ComID 243: MD request body: mdPayload object
109 Table 90 โ€“ ComID 244: MD request header telegram values
Table 91 โ€“ ComID 244: MD request Body telegram values
Table 92 โ€“ ComID 244: MD request body: mdPayload object
Table 93 โ€“ ComID 244: MD reply header telegram values
Table 94 โ€“ ComID 244: MD reply body telegram values
110 Table 95 โ€“ ComID 244: MD reply body: mdPayload object
Table 96 โ€“ ComID 245: MD request header telegram values
Table 97 โ€“ ComID 245: MD request Body telegram values
111 6.3.6 MCG Train Wake-up Service (Option)
Figure 41 โ€“ Example Procedure to wake up the train
Table 98 โ€“ ComID 245: MD request body: mdPayload object
112 7 Services and interfaces (GCG)
7.1 GCG Overview
Table 99 โ€“ ComID 238: twsWakeUp MD event header
Table 100 โ€“ ComID 238: twsWakeUp MD event body
Table 101 โ€“ ComID 238: twsWakeUp MD event body: mdPayload object
113 Figure 42 โ€“ Train to Ground interfaces
114 7.2 GCG Addressing
7.2.1 Wireless MCG Interface
7.2.2 Ground GCG Interface
115 7.3 GCG Implementation
7.3.1 General (informative)
7.3.2 GCG Availability
7.3.3 GCG Workload
7.3.4 GCG Security
7.4 GCG services
7.4.1 GCG services protocol
7.4.2 GCG Fleet Database
116 7.4.3 MCG-GCG services
7.4.4 File transfer communication service
7.4.5 Local Ground GCG Interface
117 7.4.6 Home GCG โ€“ Foreign GCG services
7.4.7 Public Ground GCG services
118 Annex A (normative)Message presentation
A.1 General
A.2 Transmission rules
A.3 Generic message
119 Annex B (normative)Telemetry data coding and ordering
B.1 General
B.2 MQTT payload coding
Figure B.1 โ€“ MQTT notification payload format
120 B.3 Variables grouping and ordering criterion
121 Figure B.2 โ€“ Example of ordering criteria
Figure B.3 โ€“ Example of values grouping
122 Table B.1 โ€“ Example of values decoding
123 Bibliography
BS EN IEC 61375-2-6:2018
$215.11