{"id":247438,"date":"2024-10-19T16:17:09","date_gmt":"2024-10-19T16:17:09","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61375-12012\/"},"modified":"2024-10-25T11:24:05","modified_gmt":"2024-10-25T11:24:05","slug":"bs-en-61375-12012","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61375-12012\/","title":{"rendered":"BS EN 61375-1:2012"},"content":{"rendered":"

This part of IEC 61375 applies to the architecture of data communication systems in open trains, i.e. it covers the architecture of a communication system for the data communication between vehicles of the said open trains, the data communication within the vehicles and the data communication from train to the ground.<\/p>\n

The applicability of this part of IEC 61375 to the train network technologies allows for interoperability of individual vehicles within open trains in international traffic. The data communication systems inside vehicles are given as recommended solutions to cope with the said TCN. In any case, proof of compatibility between a proposed train backbone and a proposed consist network will have to be brought by the supplier.<\/p>\n

This part of IEC 61375 may be additionally applicable to closed trains and multiple unit trains when so agreed between purchaser and supplier.<\/p>\n

\n

NOTE 1 For a definition of open trains, multiple unit trains and closed trains, see Clause 3.<\/p>\n

NOTE 2 Road vehicles such as buses and trolley buses are not considered in this part of IEC 61375.<\/p>\n<\/blockquote>\n

PDF Catalog<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
7<\/td>\nEnglish
CONTENTS <\/td>\n<\/tr>\n
10<\/td>\nINTRODUCTION <\/td>\n<\/tr>\n
11<\/td>\n1 Scope
2 Normative references
3 Terms, definitions, abbreviated terms, acronyms, and conventions
3.1 Terms and definitions <\/td>\n<\/tr>\n
18<\/td>\n3.2 Abbreviations and acronyms <\/td>\n<\/tr>\n
19<\/td>\n3.3 Conventions
3.3.1 Requirement conventions
3.3.2 Base of numeric values
3.3.3 Naming conventions
3.3.4 State diagram conventions
4 Basic architecture
4.1 Contents of this clause
4.2 General
4.2.1 Technology classes <\/td>\n<\/tr>\n
20<\/td>\n4.2.2 Component types
4.3 Hierarchical structure
4.3.1 Network levels
4.3.2 Train backbone level
Figures
Figure 1 \u2013 Train backbone and consist network <\/td>\n<\/tr>\n
21<\/td>\n4.3.3 Consist network level
4.3.4 Interface between train backbone and consist network
Figure 2 \u2013 Consist with two consist networks <\/td>\n<\/tr>\n
22<\/td>\n4.3.5 End devices connected to train backbone
4.4 Network configurations
Figure 3 \u2013 End device connected to the train backbone (example) <\/td>\n<\/tr>\n
23<\/td>\n4.5 Train to ground connection (option) <\/td>\n<\/tr>\n
24<\/td>\n5 Train backbone
5.1 Contents of this clause
5.2 Train backbone topology
5.2.1 General
5.2.2 Train backbone based on bus technology
Figure 4 \u2013 Communication between train and ground (example)
Figure 5 \u2013 Interfaces between consists <\/td>\n<\/tr>\n
25<\/td>\n5.2.3 Train backbone based on switched technology
5.3 Train compositions
Figure 6 \u2013 Train backbone bus topology
Figure 7 \u2013 Train backbone switched topology
Tables
Table 1 \u2013 Train composition changes <\/td>\n<\/tr>\n
26<\/td>\n5.4 Train backbone node numbering
5.5 Train directions
5.5.1 Vehicle
5.5.2 Consist
Figure 8 \u2013 Directions and orientation in a vehicle <\/td>\n<\/tr>\n
27<\/td>\n5.5.3 Closed train
5.5.4 Train
Figure 9 \u2013 Directions and orientations in a consist
Figure 10 \u2013 Directions and orientations in a closed train <\/td>\n<\/tr>\n
28<\/td>\nFigure 11 \u2013 Directions and orientations in train (TCN directions) <\/td>\n<\/tr>\n
29<\/td>\n5.6 Train inauguration
5.6.1 Objectives
5.6.2 Train network directory <\/td>\n<\/tr>\n
30<\/td>\nFigure 12 \u2013 Structure of train network directory (example)
Table 2 \u2013 Train network specific parameters (example)
Table 3 \u2013 Consist network specific parameters (example) <\/td>\n<\/tr>\n
31<\/td>\n5.6.3 Inauguration control
Table 4 \u2013 Vehicle specific parameters (example)
Table 5 \u2013 Device specific parameters (example) <\/td>\n<\/tr>\n
32<\/td>\n5.6.4 Node states <\/td>\n<\/tr>\n
33<\/td>\nFigure 13 \u2013 Train inauguration block diagram <\/td>\n<\/tr>\n
34<\/td>\nFigure 14 \u2013 Train inauguration state chart <\/td>\n<\/tr>\n
35<\/td>\n5.6.5 Node roles
5.6.6 Performance
6 Consist network
6.1 Contents of this clause
6.2 Scope of standardization <\/td>\n<\/tr>\n
36<\/td>\n6.3 Consist network topology
6.3.1 Consist network based on bus technology (MVB, CANopen)
Figure 15 \u2013 Consist network standard interfaces <\/td>\n<\/tr>\n
38<\/td>\nFigure\u00a018 \u2013 Examples of consist network topologies (switched technology)
Figure 19 \u2013 End device connected to two consist switches <\/td>\n<\/tr>\n
39<\/td>\n6.3.3 Sub-networks
6.3.4 Heterogeneous consist network
6.4 Gateway
6.4.1 General
Figure 20 \u2013 Sub-networks in a consist network
Figure 21 \u2013 Implementation example for two vehicle busses <\/td>\n<\/tr>\n
40<\/td>\n6.4.2 Functional description
6.4.3 Application layer gateway
Figure 22 \u2013 Example of heterogeneous train control network architecture <\/td>\n<\/tr>\n
41<\/td>\nFigure 23 \u2013 Local service
Figure 24 \u2013 Unconfirmed service
Figure 25 \u2013 Confirmed service <\/td>\n<\/tr>\n
42<\/td>\n6.4.4 Gateway implemented by a router
7 On-board data communication
7.1 General
7.2 Communication patterns
7.2.1 Purpose
7.2.2 Definitions
Figure 26 \u2013 Provider initiated services <\/td>\n<\/tr>\n
43<\/td>\n7.2.3 Push pattern
Figure 27 \u2013 Point to point communication pattern (push) <\/td>\n<\/tr>\n
44<\/td>\n7.2.4 Pull pattern
Figure 28 \u2013 Point to multi-point communication pattern (push)
Figure 29 \u2013 Point to point communication pattern (pull) <\/td>\n<\/tr>\n
45<\/td>\nFigure\u00a030 \u2013 Point to multi-point communication pattern (push) <\/td>\n<\/tr>\n
46<\/td>\n7.2.5 Subscription pattern
7.3 Addressing
7.3.1 General
7.3.2 Network layer addressing
Figure 31 \u2013 Subscription communication pattern <\/td>\n<\/tr>\n
48<\/td>\n7.3.3 Application layer addressing
7.4 Availability of data communication <\/td>\n<\/tr>\n
49<\/td>\n7.5 Data classes
7.5.1 General
7.5.2 Service parameters
Table 6 \u2013 Service parameters <\/td>\n<\/tr>\n
50<\/td>\n7.5.3 TCN data class definition
Table 7 \u2013 Principal data classes <\/td>\n<\/tr>\n
51<\/td>\n7.6 Communication profile <\/td>\n<\/tr>\n
52<\/td>\nBibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

Electronic railway equipment. Train communication network (TCN) – General architecture<\/b><\/p>\n\n\n\n\n
Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
BSI<\/b><\/a><\/td>\n2012<\/td>\n54<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":247442,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[775,2641],"product_tag":[],"class_list":{"0":"post-247438","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-45-060-01","7":"product_cat-bsi","9":"first","10":"instock","11":"sold-individually","12":"shipping-taxable","13":"purchasable","14":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/247438","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/247442"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=247438"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=247438"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=247438"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}