BSI PD CEN/TS 13149-7:2020
$142.49
Public transport. Road vehicle scheduling and control systems – System and network architecture
Published By | Publication Date | Number of Pages |
BSI | 2020 | 30 |
This document specifies the general rules for an on-board data communication system between the different systems that may be used within public transport vehicles, based on the Internet Protocol (IPv4, [3] and IPv6, [4]). This includes operational support systems, passenger information systems, fare collection systems, etc.
This document describes:
-
the requirements for an on board IP network;
-
the overview architecture and components for an IP based on-board network;
-
the modular structure of the network architecture;
-
the Service Oriented Architecture (SOA) approach, and approach to defining services.
Systems directly related to the safe operation of the vehicle (including propulsion management, brake systems, door opening systems) are excluded from the scope of this document and are dealt with in other standardization bodies. However, the architecture described in this document may be used for support services such as safety information messages. Interfaces to safety-critical systems should be provided through dedicated gateways with appropriate security provisions; for the purposes of this document, these are regarded as simply external information sources.
This document is designed primarily for vehicles with a fixed primary structure, where networks can be installed on a permanent basis and the system configuration task consists largely of the integration, adjustment or removal of the functional end systems that produce and/or consume data. Public transport vehicles consisting of units linked temporarily for operational purposes (specifically, trains in which individual engines, cars or consists are routinely connected and disconnected) require additional mechanisms to enable the communications network itself to reconfigure. Such mechanisms are provided through other standards, notably the IEC 61375 series [5].
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
6 | European foreword |
7 | Introduction |
9 | 1 Scope 2 Normative references 3 Terms and definitions |
11 | 4 Symbols and abbreviations |
12 | 5 Design principles 5.1 Introduction 5.2 Design goals 5.2.1 Enabling communications 5.2.2 Enabling interoperability 5.2.3 Ease of configuration 5.2.4 Quality of monitoring 5.2.5 Maintainability 5.2.6 Migration |
13 | 5.2.7 Supporting fleet changes 6 Network architecture 6.1 Introduction 6.2 Network overview 6.3 Gateways to other networks |
14 | 6.4 IP addressing 6.4.1 General addressing considerations 6.4.2 Address space |
15 | 6.4.3 Manual assignment 6.4.4 Automatic assignment |
16 | 6.5 Name registration and resolution of modules 6.5.1 Domain name options |
17 | 6.5.2 Unicast Domain Name System (DNS) 6.5.3 Multicast Domain Name System (mDNS) |
18 | 6.6 Communication Protocols 6.6.1 HyperText Transfer Protocol (HTTP) 6.6.2 File Transfer Protocol (FTP) 6.6.3 Secure Shell (SSH) 6.6.4 Multicast User Datagram Protocol (Multicast-UDP) 6.6.5 Session control |
19 | 6.6.6 Data Multicast 6.6.7 Real-time Transport Protocol (RTP) |
20 | 6.6.8 Network Time Protocol (NTP) / Simple Network Time Protocol (SNTP) 6.6.9 Message Queuing Telemetry Transport (MQTT) 6.7 Network security 6.8 Considerations on coupled vehicles |
21 | 7 Service architecture 7.1 Service oriented architecture (SOA) 7.2 Service Information 7.2.1 Service framework options 7.2.2 Manual configuration 7.2.3 Configuration using DNS-SD |
23 | 7.3 Communication Types 7.3.1 Event Triggered Data 7.3.2 Streaming of Data 7.3.3 High Frequency Data 7.4 Data Structure 7.4.1 Data structure options |
24 | 7.4.2 XML 7.4.3 JSON |
25 | Annex A (informative) Example usages |
27 | Bibliography |