Shopping Cart

No products in the cart.

BS EN 50463-4:2017 – TC:2020 Edition

$280.87

Tracked Changes. Railway applications. Energy measurement on board trains – Communication

Published By Publication Date Number of Pages
BSI 2020 358
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 European Standard applies to the on board and on board to ground communication services, i.e. it covers the data communication using digital interfaces: a) between functions implemented within the EMS; b) between EMS function and other on board subsystems; c) between EMS and ground communication services. The on board data communication services of the EMS cover the data exchange between functions of the EMS and the data exchange between EMS and other on board units, where data are exchanged using a communications protocol stack over a dedicated physical interface or a shared communication network. The on board to ground communication services cover the wireless data communication between the DHS and the on ground server. Furthermore, this document includes conformity assessment requirements.

PDF Catalog

PDF Pages PDF Title
190 National foreword
203 1 Scope
2 Normative references
204 3 Terms, definitions and abbreviations
3.1 Terms and definitions
209 3.2 Abbreviations
210 4 Requirements
4.1 General
4.2 Communication between functions of the EMS
4.2.1 General
212 4.2.2 Communication protocols stack
213 4.2.3 Communication security
4.2.3.1 General
4.2.3.2 Security implemented by software
214 4.2.4 VMF/CMF to ECF Interface (VEI)
4.2.5 EMF to DHS interface (EMDI)
4.2.6 Maintenance/testing interfaces (DSI and ESI)
215 4.2.7 DHS to location function
4.2.8 DHS to UTC source
4.2.9 DHS to Consist Network digital interface (CNI)
4.3 Communication between the EMS and ground
4.3.1 General
216 4.3.2 EMS set-up
218 4.3.3 Application services (service layer)
4.3.3.1 Services related with the transfer of CEBDs from EMS to a user on ground
4.3.3.2 Other services
219 4.3.3.3 User access rights to the application services
220 4.3.4 Data structures (data layer)
4.3.4.1 General
221 4.3.4.2 CEBDBlock
223 4.3.4.3 EventSet
230 4.3.4.4 Heartbeat
231 4.3.4.5 ReadingBlock
237 4.3.4.6 CommunicationConfig
248 4.3.4.7 ChangeCommunicationConfig
256 4.3.4.8 AssetData
265 4.3.4.9 State
270 4.3.4.10 Common definitions
272 4.3.4.11 Additional common definitions
4.3.4.12 Digital signature
273 4.3.5 Message mechanism (message layer)
4.3.5.1 General
4.3.5.2 Message mechanism methods
274 4.3.5.3 Message structure
279 4.3.5.4 Application service mapping
284 4.3.6 Application protocols for supporting the message mechanism
4.3.6.1 General
285 4.3.6.2 HTTP
287 4.3.6.3 FTP with mailbox
290 4.3.6.4 Encryption
4.3.7 Communication architecture
4.3.7.1 General
291 4.3.7.2 Dedicated wireless connection
293 4.3.7.3 EMS addressing
4.3.7.4 GS Addressing
4.3.8 XML schema version control
294 4.3.9 Security
4.4 Access security
5 Conformity assessment
5.1 General
5.1.1 Introduction
5.1.2 Applicability
295 5.1.3 Methodology
5.2 PICS and PIXIT
5.2.1 General
5.2.2 PICS
5.2.3 PIXIT
296 5.3 Design review
5.4 Type test procedure
5.4.1 General
5.4.2 Testing the communication
5.4.3 Testing the on board interfaces
5.4.3.1 General
5.4.3.2 Test bench
297 5.4.3.3 Abstract test suites
5.4.4 Testing the on board to ground interface
5.4.4.1 General
5.4.4.2 Test benches
298 5.4.4.3 Abstract test suites
299 Annex A (informative)VEI–VMF/CMF to ECF interface implementation example
A.1 General
A.2 Payload format
300 A.3 Encryption
301 Annex B (informative)PICS structure and instruction
B.1 Structure
B.2 Instructions for completing the PICS pro-forma
B.2.1 PICS table structure
B.2.2 Abbreviations used in PICS
302 B.2.3 Ref. column
B.2.4 Subclause column
B.2.5 Capability column
B.2.6 Requirement column
B.2.7 Implementation column
303 B.2.8 Parameter values column
B.2.8.1 Allowed min
B.2.8.2 Default value
B.2.8.3 Allowed max
B.2.8.4 Implemented value
B.3 PICS pro-forma examples
B.3.1 Identification of PICS
B.3.2 Identification of the implementation under assessment
304 B.3.3 Identification of the IUA supplier
305 B.3.4 Identification of the standards
B.3.5 Global statement of conformity
B.3.6 Level of conformity
306 Annex C (informative)Access rights
307 Annex D (normative)XML schemas of the message mechanism
D.1 General
D.2 Message.xsd
309 Annex E (normative)XML schemas of the mandatory data structures
E.1 General
E.2 50463_BaseType.xsd
311 E.3 CEBDBlock.xsd
312 E.4 EventSet.xsd
E.5 Heartbeat.xsd
314 Annex F (normative)XML schemas of the optional data structures
F.1 General
F.2 50463_BaseTypes_Extension.xsd
315 F.3 ReadingBlock.xsd
317 F.4 CommunicationConfig.xsd
322 F.5 ChangeCommunicationConfig.xsd
327 F.6 AssetData.xsd
330 F.7 State.xsd
332 Annex G (informative)On board to ground communication XML examples
G.1 General
G.2 Examples of data structures
G.2.1 CEBDBlock
335 G.2.2 EventSet
336 G.2.3 Heartbeat
G.2.4 ReadingBlock
340 G.2.5 CommunicationConfig
343 G.2.6 ChangeCommunicationConfig
344 G.2.7 AssetData
348 G.2.8 State
349 G.3 Examples of application services
G.3.1 AutomaticTransferCEBDBlocks
G.3.2 AutomaticTransferEvents
G.3.3 AutomaticTransferHeartbeat
350 G.3.4 PeriodicTransferState
G.3.5 RequestCEBDBlocks
351 G.3.6 RequestAssetData
G.3.7 RequestEvents
352 G.3.8 ChangeCommunicationConfig
354 Annex ZZ (informative)Relationship between this European Standard and the Essential Requirements of Directive 2008/57/EC
BS EN 50463-4:2017 - TC
$280.87