BSI PD CEN/TS 17466:2020
$189.07
Intelligent transport systems. Urban ITS. Communication interfaces and profiles for traffic management
Published By | Publication Date | Number of Pages |
BSI | 2020 | 48 |
This document identifies traffic management interfaces between central stations and specifies related ITS communication profiles enabling standardized data exchange over these communication interfaces, applicable for a variety of platforms including ITS station units (ITS-SUs) compliant with ISO 21217:2014. This document further specifies requirements on encoding of data.
These traffic management interfaces enable
-
the provision of appropriate and relevant traffic information, e.g. congestion and travel times, to users across a variety of platforms;
-
exchange of data such as:
-
network performance data, e.g. traffic conditions, travel times, and
-
planned and unplanned events and incidents, e.g.
-
roadworks,
-
closures of roads, bridges, and tunnels,
-
bad weather,
-
road surface conditions.
-
-
This document recognizes specifications from DATEX II in order to avoid duplicate specifications. In doing so, this document aligns with existing products of CEN/TC 278/WG 8 and the additional work being undertaken within the DATEX community.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
9 | 1 Scope 2 Normative references |
10 | 3 Terms and definitions |
11 | 4 Symbols and abbreviations |
13 | 5 Traffic management interfaces 5.1 Basics on traffic management 5.2 Basics on interfaces |
14 | 5.3 Interactions between TM actors 5.4 ITS-S Communication Profiles 6 Use cases 6.1 Domains within traffic management |
15 | 6.2 Operational activities 6.2.1 Overview |
16 | 6.2.2 Status gathering 6.2.3 Data retrieval 6.2.4 Control |
17 | 7 Data and communication protocols 7.1 Data models 7.1.1 DATEX II 7.1.2 OCIT-C |
19 | 7.1.3 UTMC |
20 | 7.1.4 DIASER 7.1.5 Other data models 7.2 Mapping data models to communications protocols |
21 | 8 Application programming interfaces 8.1 Introduction 8.2 Data exchange 8.3 Filtering |
22 | 8.4 Version management 8.5 Security mechanisms 8.6 ITS-S facilities 8.6.1 HTTP 8.6.2 MQTT 8.6.3 AMQP 8.6.4 SOAP 8.6.5 RESTful |
23 | 8.7 Communications features |
24 | 9 Encodings 9.1 Interfaces using XML encoding 9.1.1 Role 9.1.2 XML specification 9.2 Interfaces using JSON encoding 9.2.1 Role |
25 | 9.2.2 Relation to DATEX II implementations 9.2.3 JSON encoding for xsd data definitions 10 Communication interfaces, triple solutions and communication profiles 10.1 Concept of triple solutions |
27 | 10.2 Triple solutions for traffic management 10.3 Communication protocol stacks |
29 | 10.4 Communication profile specifications |
30 | Annex A (informative)DATEX – JSON mapping A.1 Initial developments in the DATEX group A.2 JSON Schema definition mapping A.2.1 Introduction A.2.2 Mapping of “D2Datatype” A.2.2.1 General |
31 | A.2.2.2 Mapping of datatypes table |
32 | A.2.2.3 Mapping of datatypes, schemaTypeInclude table |
33 | A.2.3 Mapping of “D2Enumeration” and “D2Literal” |
34 | A.2.4 Mapping of “D2Enumeration” and “D2Literal” |
35 | A.2.5 Mapping of “D2Class” A.2.5.1 General A.2.5.2 “D2Class” classes without superclass |
37 | A.2.5.3 “D2Class” classes with superclass |
38 | A.2.5.4 “D2Class” classes which are superclasses A.2.6 Mapping of “D2Identifiable” and “D2VersionedIdentifiable” classes |
40 | A.2.7 Root instances A.2.8 Extension mapping A.2.8.1 General A.2.8.2 Extension mapping for Classes |
41 | A.2.8.3 Extension mapping for Enumerations A.2.9 Overall document structure and namespaces |