{"id":247764,"date":"2024-10-19T16:18:47","date_gmt":"2024-10-19T16:18:47","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61375-2-62018\/"},"modified":"2024-10-25T11:26:28","modified_gmt":"2024-10-25T11:26:28","slug":"bs-en-iec-61375-2-62018","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61375-2-62018\/","title":{"rendered":"BS EN IEC 61375-2-6:2018"},"content":{"rendered":"
This part of IEC 61375 establishes the specification for the communication between the on-board subsystems and the ground subsystems.<\/p>\n
The communication system, interfaces and protocols are specified as a mobile communication function, using any available wireless technology.<\/p>\n
This document provides requirements in order to:<\/p>\n
select the wireless network on the basis of QoS parameters requested by the application;<\/p>\n<\/li>\n
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;<\/p>\n<\/li>\n
allow applications running on ground installations to have a remote access to the TCMS and\/or OMTS applications installed on-board.<\/p>\n<\/li>\n<\/ol>\n
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.<\/p>\n
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.<\/p>\n
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.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 3.2 Symbols and abbreviated terms <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 3.3 State diagram conventions 4 Board to Ground Communication system architecture 4.1 General 4.2 Requirements <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Tables Table 1 \u2013 Board to ground requirements <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 4.3 Mobile communication network architecture 4.3.1 General 4.3.2 On-board network interface Figures Figure 1 \u2013 Train on-board communication system (example) <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 4.4 System breakdown structure 4.4.1 General Figure 2 \u2013 Ground communication system (example) <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 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 \u2013 Board-to-ground system breakdown Table 3 \u2013 MCG sub-system breakdown Table 4 \u2013 GCG sub-system breakdown <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 4.6 Mobile Communication Gateway 4.6.1 Architecture Table 5 \u2013 An example of the MCG function breakdown Table 6 \u2013 An example of the GCG function breakdown <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Figure 3 \u2013 Option 1: End device board to ground communication via MCG <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 4.6.2 Mobile communication gateway Figure 4 \u2013 Option 2: End Device board to ground communicationvia dedicated interface <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Figure 5 \u2013 MCG abstract model block diagram Figure 6 \u2013 MCG configured as ALG <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 4.7 Mobile communication redundancy 4.7.1 General Figure 7 \u2013 Architectural example of redundant Board to Ground communication <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 4.7.2 Full performance redundancy 4.7.3 Reduced performance redundancy 4.8 Train composition changes Table 7 \u2013 Device \u2013 status of implementation of the TIS Table 8 \u2013 Composition \u2013 status of implementation of the TIS <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 4.9 Security 4.9.1 Security zones <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 4.9.2 Security measures Figure 8 \u2013 Security zones (simplified) <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Table 9 \u2013 Security measures <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 4.9.3 Authentication authorization accounting model <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 9 \u2013 Authentication, authorization and accounting model <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 4.9.4 Network and MCG classification Table 10 \u2013 MCG categories <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure 10 \u2013 MCG connecting open and closed transmission systems Table 11 \u2013 Security requirements <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 5 Communication framework 5.1 General 5.2 MCG broker service architecture <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 5.3 Addressing concept 5.3.1 Use cases Figure 11 \u2013 MCG broker service architecture <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 5.3.2 Consist and train Identification 5.3.3 T2G Network Borders 5.3.4 T2G basic minimum network Figure 12 \u2013 Minimum Train to Ground Network Setup <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 5.3.5 T2G addressing Figure 13 \u2013 A train consisting of four vehicles <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 5.3.6 HTTP-URI Table 12 \u2013 TCN-URI global DNS zone <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 5.4 Data classes for T2G communication 5.4.1 General 5.4.2 Communication channel establishment 5.4.3 Message data <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 5.4.4 Process data Table 13 \u2013 Recommended service parameters for message data <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 5.4.5 Stream Data 5.4.6 Best effort data Table 14 \u2013 Recommended service parameters for process data Table 15 \u2013 Recommended service parameters for stream data <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 5.5 Communication protocol 5.5.1 General 5.5.2 HTTP(S) Table 16 \u2013 Recommended service parameters for best effort data <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Figure 14 \u2013 Communication stacks Figure 15 \u2013 HTTP(S) MD communication pattern <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 5.5.3 MQTT (Option) Figure 16 \u2013 HTTP(S) request\/event Figure 17 \u2013 HTTP(S) response Table 17 \u2013 HTTP(S) parameters request\/response pattern <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 5.6 Communication services 5.6.1 General 5.6.2 Message data communication service <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Figure 18 \u2013 Message Data exchange (example) <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Figure 19 \u2013 Message Data telegram structure Table 18 \u2013 General MD Header <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Table 19 \u2013 General MD Body Table 20 \u2013 MD Checksum Table 21 \u2013 Message types <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 5.6.3 File transfer communication service Table 22 \u2013 Message representation Table 23 \u2013 File transfer terminology <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Figure 20 \u2013 File upload example <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Table 24 \u2013 ComID 202: MD header telegram values Table 25 \u2013 ComID 202: MD body telegram values <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Table 26 \u2013 ComID 202: MD body: mdPayload object Table 27 \u2013 ComID 203: MD header telegram values Table 28 \u2013 ComID 203: MD body telegram values <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Table 29 \u2013 ComID 203: MD body: mdPayload object Table 30 \u2013 ComID 206: MD header telegram values Table 31 \u2013 ComID 206: MD body telegram values <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Table 32 \u2013 ComID 206: MD body: mdPayload object Table 33 \u2013 ComID 207: MD header telegram values Table 34 \u2013 ComID 207: MD body telegram values <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Figure 21 \u2013 Error case: No ComID 203 received Table 35 \u2013 ComID 207: MD body: mdPayload object <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Figure 22 \u2013 Error case: no ComID 206 received, no file uploaded to the wayside <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Figure 23 \u2013 Error Case: No ComID 206 received, file uploaded to the wayside <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Figure 24 \u2013 Error Case: No ComID 207 received <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Figure 25 \u2013 File download example <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table 36 \u2013 ComID 208: MD header telegram values Table 37 \u2013 ComID 208: MD Body telegram values <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table 38 \u2013 ComID 208: MD Body: mdPayload object Table 39 \u2013 ComID 209: MD header telegram values <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Table 40 \u2013 ComID 209: MD Body telegram values Table 41 \u2013 ComID 209: MD Body: mdPayload object Table 42 \u2013 ComID 210: MD header telegram values <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Table 43 \u2013 ComID 210: MD Body telegram values Table 44 \u2013 ComID 210: MD Body: mdPayload object Table 45 \u2013 ComID 211: MD header telegram values Table 46 \u2013 ComID 211: MD Body telegram values <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 47 \u2013 ComID 211: MD Body: mdPayload object <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Figure 26 \u2013 Error case: no ComID 209 received <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Figure 27 \u2013 Error case: no ComID 211 received <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Figure 28 \u2013 Error case: no ComID 210 received <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table 48 \u2013 Main parts of dlTarget URI Table 49 \u2013 Main parts of host element <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table 50 \u2013 Valid \u201cdevice\u201d label values Table 51 \u2013 Valid \u201cvehicle\u201d label values Table 52 \u2013 Valid \u201cconsist\u201d label values <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | 6 Services and interfaces (MCG) 6.1 Overview 6.1.1 MCG system service architecture Table 53 \u2013 Valid \u201cclosed train\u201d label values Table 54 \u2013 Valid \u201ctrain\u201d label values Table 55 \u2013 Exemplary dlTarget values <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | 6.1.2 MCG \/ GCG system service interfaces Figure 29 \u2013 Service architecture <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | 6.1.3 MCG \/ GCG communication relationship 6.2 Service provisioning Figure 30 \u2013 Service interfaces <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 6.3 MCG \/ GCG system service description 6.3.1 Communication Services <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Figure 31 \u2013 Procedure to establish the radio link from MCG Figure 32 \u2013 Procedure to establish the radio link from GCG <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Figure 33 \u2013 Procedure to update the ground DNS server Table 56 \u2013 ComID 240: Capability message <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | 6.3.2 Train Location Service (Option) Table 57 \u2013 ComID 240: MD event body telegram values Table 58 \u2013 ComID 240: MD event body: mdPayload object <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure 34 \u2013 Example architecture to provide the train location <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Figure 35 \u2013 Example procedure to notify about current train location <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Table 59 \u2013 ComID 230: MD request header telegram values Table 60 \u2013 ComID 230: MD request body telegram values Table 61 \u2013 ComID 230: MD request body: mdPayload object <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Table 62 \u2013 ComID 230: MD reply header telegram values Table 63 \u2013 ComID 230: MD reply body telegram values Table 64 \u2013 ComID 230\/232: MD reply\/notification body: mdPayload object <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Table 65 \u2013 Example of latitude\/longitude with proposed fixed point notation Table 66 \u2013 ComID 232: MD header telegram values Table 67 \u2013 ComID 232: MD Body telegram values <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | 6.3.3 Train Information Service Figure 36 \u2013 Example architecture to notify about train information <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Figure 37 \u2013 Example procedure to notify about train information <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Table 68 \u2013 ComID 234: MD request header telegram values Table 69 \u2013 ComID 234: MD request body telegram values Table 70 \u2013 ComID 234: MD request body: mdPayload object Table 71 \u2013 ComID 234: MD reply header telegram values <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Table 72 \u2013 ComID 234: MD reply body telegram values Table 73 \u2013 ComID 234: MD reply body: mdPayload object <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | 6.3.4 MCG Network Selector Service Table 74 \u2013 ComID 236: MD header telegram values Table 75 \u2013 ComID 236: MD Body telegram values <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure 38 \u2013 Illustration of network selector <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | 6.3.5 Train telemetry service (Option) Figure 39 \u2013 Architecture to provide telemetry data <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Figure 40 \u2013 Procedure to notify about current train location <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Table 76 \u2013 ComID 240: MD request header telegram values Table 77 \u2013 ComID 240: MD request Body telegram values <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Table 78 \u2013 ComID 240: MD reply header telegram values Table 79 \u2013 ComID 240: MD reply body telegram values Table 80 \u2013 ComID 240: MD reply body: mdPayload object <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Table 81 \u2013 ComID 242: MD request header telegram values Table 82 \u2013 ComID 242: MD request Body telegram values <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Table 83 \u2013 ComID 242: MD request body: mdPayload object Table 84 \u2013 ComID 242: MD reply header telegram values <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Table 85 \u2013 ComID 242: MD reply body telegram values Table 86 \u2013 ComID 242: MD reply body: mdPayload object <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | Table 87 \u2013 ComID 243: MD request header telegram values Table 88 \u2013 ComID 243: MD request Body telegram values Table 89 \u2013 ComID 243: MD request body: mdPayload object <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Table 90 \u2013 ComID 244: MD request header telegram values Table 91 \u2013 ComID 244: MD request Body telegram values Table 92 \u2013 ComID 244: MD request body: mdPayload object Table 93 \u2013 ComID 244: MD reply header telegram values Table 94 \u2013 ComID 244: MD reply body telegram values <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Table 95 \u2013 ComID 244: MD reply body: mdPayload object Table 96 \u2013 ComID 245: MD request header telegram values Table 97 \u2013 ComID 245: MD request Body telegram values <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | 6.3.6 MCG Train Wake-up Service (Option) Figure 41 \u2013 Example Procedure to wake up the train Table 98 \u2013 ComID 245: MD request body: mdPayload object <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | 7 Services and interfaces (GCG) 7.1 GCG Overview Table 99 \u2013 ComID 238: twsWakeUp MD event header Table 100 \u2013 ComID 238: twsWakeUp MD event body Table 101 \u2013 ComID 238: twsWakeUp MD event body: mdPayload object <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Figure 42 \u2013 Train to Ground interfaces <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | 7.2 GCG Addressing 7.2.1 Wireless MCG Interface 7.2.2 Ground GCG Interface <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | 7.4.3 MCG-GCG services 7.4.4 File transfer communication service 7.4.5 Local Ground GCG Interface <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | 7.4.6 Home GCG \u2013 Foreign GCG services 7.4.7 Public Ground GCG services <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Annex A (normative)Message presentation A.1 General A.2 Transmission rules A.3 Generic message <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | Annex B (normative)Telemetry data coding and ordering B.1 General B.2 MQTT payload coding Figure B.1 \u2013 MQTT notification payload format <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | B.3 Variables grouping and ordering criterion <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Figure B.2 \u2013 Example of ordering criteria Figure B.3 \u2013 Example of values grouping <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | Table B.1 \u2013 Example of values decoding <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Electronic railway equipment. Train communication network (TCN) – On-board to ground communication<\/b><\/p>\n |