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.<\/p>\n
It identifies existing open specifications for<\/p>\n
sensor systems;<\/p>\n<\/li>\n
traffic control;<\/p>\n<\/li>\n
traffic information;<\/p>\n<\/li>\n
public transport information;<\/p>\n<\/li>\n
distributed C-ITS;<\/p>\n<\/li>\n
central systems.<\/p>\n<\/li>\n<\/ul>\n
It provides common specifications of<\/p>\n
sensor systems;<\/p>\n<\/li>\n
traffic control;<\/p>\n<\/li>\n
traffic information;<\/p>\n<\/li>\n
public transport information;<\/p>\n<\/li>\n
distributed C-ITS;<\/p>\n<\/li>\n
central systems.<\/p>\n<\/li>\n<\/ul>\n
It describes openly plied proprietary standards and extant communications protocols that can be used in mixed vendor environments in the context of U-ITS.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 4 Symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 5 Requirements 6 Context 6.1 Background 6.2 Interoperability requirements in the traffic management domain <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 6.3 Communication standards for traffic management 6.3.1 General overview on communication standards <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 6.3.2.6 Parking management 6.3.2.7 Ramp meter monitoring and control 6.3.2.8 Real-time passenger information <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 6.3.2.9 Real-time traffic monitoring <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 6.3.2.10 Rising bollards and barrier control <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7.3 Use-case specific data model requirements 7.3.1 Simple Network Management Protocol <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 7.3.15 Binary container 7.3.16 Distributed C-ITS via a secured ITS domain 7.3.17 Central systems 7.4 NTCIP <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 8 Open specifications for sensor systems 8.1 Introduction 8.2 Existing open specifications 8.2.1 OCIT 8.2.2 UTMC <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 8.2.3 ONVIF 8.2.4 DIASER 8.2.5 Other European regional standards 9 Open specifications for traffic control 9.1 Introduction <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 9.2 Existing open specifications 9.2.1 DATEX II <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 9.2.2 OCIT-outstations V3.0 <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 9.2.3 UTMC 9.2.4 IVERA <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 9.2.5 DIASER 9.2.6 RSMP 9.2.7 NTCIP <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 10 Open specifications for traffic information 10.1 Introduction 10.2 Existing open specifications 10.2.1 OCIT 10.2.2 UTMC <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 11.2.2 SIRI <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 11.2.3 NeTEx <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 11.2.4 RTIG <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 12.2 Existing open specifications 12.2.1 Overview <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 13.3 OCIT-C <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 13.4 UTMC <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 13.5 NTCIP 14 Openly plied proprietary standards 14.1 Introduction 14.2 General transit feed specification (GTFS) <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 14.3 JAVA <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | 14.4 Bluetooth <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 14.5 Common specification <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | Annex A (informative)NTCIP A.1 Background A.2 NTCIP Standards Framework <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | A.3 NTCIP Communications Standards A.3.1 \u2018Center to Field\u2019 Device Communications <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | A.3.2 NTCIP \u2018Center to Center\u2019 Communications <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | Annex B (informative)Traffic signal controller interface B.1 Background B.1.1 Justification B.1.2 Design approach and history <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | B.1.3 Status B.2 Implementation and usage B.2.1 Physical implementation <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | B.2.2 Role in an traffic systems B.2.3 Connection with associated standards <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | B.3 Data model <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | B.4 Data Dictionary for TrafficSignalStatusPublication B.4.1 TrafficSignalStatusPublication B.4.1.1 \u201cTrafficSignalStatusPublication\u201d package classes B.4.1.2 \u201cTrafficSignalStatusPublication\u201d package association roles B.4.1.3 \u201cTrafficSignalStatusPublication\u201d package attributes B.4.2 TrafficSignalStatus B.4.2.1 \u201cTrafficSignalStatus\u201d classes <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | B.4.2.2 \u201cTrafficSignalStatus\u201d association roles B.4.2.3 \u201cTrafficSignalStatus\u201d attributes B.4.3 TrafficSignalFault B.4.3.1 \u201cTrafficSignalFault\u201d classes B.4.3.2 \u201cTrafficSignalFault\u201d association roles B.4.3.3 \u201cTrafficSignalFault\u201d attributes <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | B.4.4 TrafficSignalConfiguration B.4.4.1 \u201cTrafficSignalConfiguration\u201d classes B.4.4.2 \u201cTrafficSignalConfiguration\u201d association roles B.4.4.3 \u201cTrafficSignalConfiguration\u201d attributes B.4.5 TrafficSignalDynamicState B.4.5.1 \u201cTrafficSignalDynamicState\u201d classes B.4.5.2 \u201cTrafficSignalDynamicState\u201d association roles <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | B.4.5.3 \u201cTrafficSignalDynamicState\u201d attributes <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | B.4.5.4 Explanation of PlanLine and SignalGroupTimings B.5 Data Dictionary of < > for TrafficSignalStatusPublication B.5.1 The < > \u201cTrafficSignalFaultEnum\u201d <\/td>\n<\/tr>\n | ||||||
| 73<\/td>\n | B.5.2 The < > \u201cTrafficSignalTypeEnum\u201d B.5.3 The < > \u201cTrafficSignalModeEnum\u201d <\/td>\n<\/tr>\n | ||||||
| 74<\/td>\n | B.5.4 The < > \u201cTrafficSignalSubModeEnum\u201d <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | B.5.5 TrafficSignalModeEnum and TrafficSignalSubModeEnum <\/td>\n<\/tr>\n | ||||||
| 76<\/td>\n | B.6 XSD <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Intelligent transport systems. Urban ITS. Use of regional traffic standards in a mixed vendor environment<\/b><\/p>\n |