{"id":231786,"date":"2024-10-19T15:05:59","date_gmt":"2024-10-19T15:05:59","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-cen-ts-174662020\/"},"modified":"2024-10-25T09:27:14","modified_gmt":"2024-10-25T09:27:14","slug":"bsi-pd-cen-ts-174662020","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-cen-ts-174662020\/","title":{"rendered":"BSI PD CEN\/TS 17466:2020"},"content":{"rendered":"
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.<\/p>\n
These traffic management interfaces enable<\/p>\n
the provision of appropriate and relevant traffic information, e.g. congestion and travel times, to users across a variety of platforms;<\/p>\n<\/li>\n
exchange of data such as:<\/p>\n
network performance data, e.g. traffic conditions, travel times, and<\/p>\n<\/li>\n
planned and unplanned events and incidents, e.g.<\/p>\n
roadworks,<\/p>\n<\/li>\n
closures of roads, bridges, and tunnels,<\/p>\n<\/li>\n
bad weather,<\/p>\n<\/li>\n
road surface conditions.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
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.<\/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 | ||||||
10<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 4 Symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 5 Traffic management interfaces 5.1 Basics on traffic management 5.2 Basics on interfaces <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 5.3 Interactions between TM actors 5.4 ITS-S Communication Profiles 6 Use cases 6.1 Domains within traffic management <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 6.2 Operational activities 6.2.1 Overview <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 6.2.2 Status gathering 6.2.3 Data retrieval 6.2.4 Control <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 7 Data and communication protocols 7.1 Data models 7.1.1 DATEX II 7.1.2 OCIT-C <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 7.1.3 UTMC <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 7.1.4 DIASER 7.1.5 Other data models 7.2 Mapping data models to communications protocols <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 8 Application programming interfaces 8.1 Introduction 8.2 Data exchange 8.3 Filtering <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 8.7 Communications features <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 10.2 Triple solutions for traffic management 10.3 Communication protocol stacks <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 10.4 Communication profile specifications <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 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 \u201cD2Datatype\u201d A.2.2.1 General <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | A.2.2.2 Mapping of datatypes table <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | A.2.2.3 Mapping of datatypes, schemaTypeInclude table <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | A.2.3 Mapping of \u201cD2Enumeration\u201d and \u201cD2Literal\u201d <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | A.2.4 Mapping of \u201cD2Enumeration\u201d and \u201cD2Literal\u201d <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | A.2.5 Mapping of \u201cD2Class\u201d A.2.5.1 General A.2.5.2 \u201cD2Class\u201d classes without superclass <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | A.2.5.3 \u201cD2Class\u201d classes with superclass <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | A.2.5.4 \u201cD2Class\u201d classes which are superclasses A.2.6 Mapping of \u201cD2Identifiable\u201d and \u201cD2VersionedIdentifiable\u201d classes <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | A.2.7 Root instances A.2.8 Extension mapping A.2.8.1 General A.2.8.2 Extension mapping for Classes <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | A.2.8.3 Extension mapping for Enumerations A.2.9 Overall document structure and namespaces <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Intelligent transport systems. Urban ITS. Communication interfaces and profiles for traffic management<\/b><\/p>\n |