BSI PD CEN/TS 17402:2020
$215.11
Intelligent transport systems. Urban ITS. Use of regional traffic standards in a mixed vendor environment
Published By | Publication Date | Number of Pages |
BSI | 2020 | 106 |
This document provides a background to the relevance of standards concerning mixed vendor environments in the context of urban-ITS. It describes key mixed vendor environments interfaces.
It identifies existing open specifications for
-
sensor systems;
-
traffic control;
-
traffic information;
-
public transport information;
-
distributed C-ITS;
-
central systems.
It provides common specifications of
-
sensor systems;
-
traffic control;
-
traffic information;
-
public transport information;
-
distributed C-ITS;
-
central systems.
It describes openly plied proprietary standards and extant communications protocols that can be used in mixed vendor environments in the context of U-ITS.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
9 | 1 Scope 2 Normative references |
12 | 3 Terms and definitions |
14 | 4 Symbols and abbreviations |
16 | 5 Requirements 6 Context 6.1 Background 6.2 Interoperability requirements in the traffic management domain |
17 | 6.3 Communication standards for traffic management 6.3.1 General overview on communication standards |
19 | 6.3.2 Use-case-specific communication standards 6.3.2.1 Active traffic management 6.3.2.2 Arterial road management 6.3.2.3 Control zone management 6.3.2.4 Dynamic message sign monitoring and control 6.3.2.5 Incident monitoring |
20 | 6.3.2.6 Parking management 6.3.2.7 Ramp meter monitoring and control 6.3.2.8 Real-time passenger information |
21 | 6.3.2.9 Real-time traffic monitoring |
22 | 6.3.2.10 Rising bollards and barrier control |
23 | 6.3.2.11 Road Weather Information System monitoring 6.3.2.12 Speed limit: Variable speed limits 6.3.2.13 Traffic camera monitoring and control 6.3.2.14 Bus gate/lane camera 6.3.2.15 Traffic signal monitoring and control 6.3.2.16 Traffic optimization |
24 | 6.3.2.17 Tunnels and bridges 6.3.2.18 Variable-message sign 7 Data model requirements 7.1 General 7.2 DATEX II 7.2.1 General |
25 | 7.2.2 DATEX II standards CEN/TS 16157 7.2.2.1 Part 1: Context and framework 7.2.2.2 Part 2: Location referencing 7.2.2.3 Part 3: Situation Publication 7.2.2.4 Part 4: Variable Message Sign (VMS) Publications |
26 | 7.2.2.5 Part 5: Measured and elaborated data publications 7.2.2.6 Part 6: Parking Publications 7.2.2.7 Part 7: Common data elements 7.2.2.8 Part 8: Traffic management publications and extensions dedicated to the urban environment 7.2.2.9 Part 9: Traffic signal management publications dedicated to the urban environment |
27 | 7.3 Use-case specific data model requirements 7.3.1 Simple Network Management Protocol |
28 | 7.3.2 Traffic messages 7.3.3 Traffic data 7.3.4 Parking data 7.3.5 Weather and environment data 7.3.6 Cameras 7.3.7 Situations and strategies |
29 | 7.3.8 Operating messages 7.3.9 Ramp metering 7.3.10 Signs (VMS) 7.3.11 Public transport passenger information 7.3.12 Traffic signal systems (TSS) 7.3.13 Traffic signal systems raw data 7.3.14 Traffic signal systems configuration data |
30 | 7.3.15 Binary container 7.3.16 Distributed C-ITS via a secured ITS domain 7.3.17 Central systems 7.4 NTCIP |
31 | 8 Open specifications for sensor systems 8.1 Introduction 8.2 Existing open specifications 8.2.1 OCIT 8.2.2 UTMC |
32 | 8.2.3 ONVIF 8.2.4 DIASER 8.2.5 Other European regional standards 9 Open specifications for traffic control 9.1 Introduction |
33 | 9.2 Existing open specifications 9.2.1 DATEX II |
34 | 9.2.2 OCIT-outstations V3.0 |
36 | 9.2.3 UTMC 9.2.4 IVERA |
38 | 9.2.5 DIASER 9.2.6 RSMP 9.2.7 NTCIP |
39 | 10 Open specifications for traffic information 10.1 Introduction 10.2 Existing open specifications 10.2.1 OCIT 10.2.2 UTMC |
40 | 10.2.3 Other European regional standards 11 Open specifications for public transport information systems 11.1 Introduction 11.2 Existing open specifications 11.2.1 Transmodel |
41 | 11.2.2 SIRI |
42 | 11.2.3 NeTEx |
43 | 11.2.4 RTIG |
44 | 11.2.5 GTFS 11.2.6 PT1711 New Modes 12 Open specifications for distributed C-ITS 12.1 Distributed C-ITS via a secured ITS domain |
45 | 12.2 Existing open specifications 12.2.1 Overview |
46 | 12.2.2 References for C-ITS related to the ITS-S access layer 12.2.3 References for C-ITS related to the ITS-S networking and transport layer 12.2.4 References for C-ITS related to the ITS-S facilities layer |
47 | 12.2.5 References for C-ITS related to the ITS-S management entity 12.2.6 References for C-ITS related to the ITS-S security entity 12.2.7 References for C-ITS related to other issues |
48 | 13 Open specifications for central systems 13.1 Transmodel and related standards for public transport 13.2 TPEG 13.2.1 TPEG 1 13.2.2 TPEG Generation 2 |
49 | 13.3 OCIT-C |
50 | 13.4 UTMC |
51 | 13.5 NTCIP 14 Openly plied proprietary standards 14.1 Introduction 14.2 General transit feed specification (GTFS) |
52 | 14.3 JAVA |
53 | 14.4 Bluetooth |
54 | 14.5 Common specification |
55 | Annex A (informative)NTCIP A.1 Background A.2 NTCIP Standards Framework |
57 | A.3 NTCIP Communications Standards A.3.1 ‘Center to Field’ Device Communications |
61 | A.3.2 NTCIP ‘Center to Center’ Communications |
62 | Annex B (informative)Traffic signal controller interface B.1 Background B.1.1 Justification B.1.2 Design approach and history |
63 | B.1.3 Status B.2 Implementation and usage B.2.1 Physical implementation |
64 | B.2.2 Role in an traffic systems B.2.3 Connection with associated standards |
65 | B.3 Data model |
67 | B.4 Data Dictionary for TrafficSignalStatusPublication B.4.1 TrafficSignalStatusPublication B.4.1.1 “TrafficSignalStatusPublication” package classes B.4.1.2 “TrafficSignalStatusPublication” package association roles B.4.1.3 “TrafficSignalStatusPublication” package attributes B.4.2 TrafficSignalStatus B.4.2.1 “TrafficSignalStatus” classes |
68 | B.4.2.2 “TrafficSignalStatus” association roles B.4.2.3 “TrafficSignalStatus” attributes B.4.3 TrafficSignalFault B.4.3.1 “TrafficSignalFault” classes B.4.3.2 “TrafficSignalFault” association roles B.4.3.3 “TrafficSignalFault” attributes |
69 | B.4.4 TrafficSignalConfiguration B.4.4.1 “TrafficSignalConfiguration” classes B.4.4.2 “TrafficSignalConfiguration” association roles B.4.4.3 “TrafficSignalConfiguration” attributes B.4.5 TrafficSignalDynamicState B.4.5.1 “TrafficSignalDynamicState” classes B.4.5.2 “TrafficSignalDynamicState” association roles |
70 | B.4.5.3 “TrafficSignalDynamicState” attributes |
72 | B.4.5.4 Explanation of PlanLine and SignalGroupTimings B.5 Data Dictionary of < > for TrafficSignalStatusPublication B.5.1 The < > “TrafficSignalFaultEnum” |
73 | B.5.2 The < > “TrafficSignalTypeEnum” B.5.3 The < > “TrafficSignalModeEnum” |
74 | B.5.4 The < > “TrafficSignalSubModeEnum” |
75 | B.5.5 TrafficSignalModeEnum and TrafficSignalSubModeEnum |
76 | B.6 XSD |