Intelligent transport systems - Urban ITS - Communication interfaces and profiles for traffic management

a) A TM interface standard to enable exchange network performance data (e.g. traffic conditions, travel times) and planned and unplanned events/incidents (e.g. roadworks, road/bridge/tunnel closures, bad weather, road surface conditions) which are not currently covered by DATEX II.
b) A TM interface standard to enable the provision of appropriate and relevant traffic information (e.g. congestion and travel times) to users, across a variety of platforms.

Intelligente Verkehrssysteme - Verkehrsmanagement-Systeme - TM-Schnittstellen und Informationen

Systèmes de transport intelligents - Systèmes de gestion du trafic - Interfaces et informations sur la MT

Inteligentni transportni sistemi - Mestni ITS - Komunikacijski vmesniki in profili za upravljanje prometa

General Information

Status
Published
Publication Date
10-Jun-2020
Technical Committee
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
14-May-2020
Due Date
19-Jul-2020
Completion Date
11-Jun-2020

Buy Standard

Technical specification
SIST-TS CEN/TS 17466:2020 - BARVE na PDF-str 26
English language
44 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST-TS CEN/TS 17466:2020
01-julij-2020

Inteligentni transportni sistemi - Mestni ITS - Komunikacijski vmesniki in profili za

upravljanje prometa

Intelligent transport systems - Urban ITS - Communication interfaces and profiles for

traffic management

Intelligente Verkehrssysteme - Verkehrsmanagement-Systeme - TM-Schnittstellen und

Informationen

Systèmes de transport intelligents - Systèmes de gestion du trafic - Interfaces et

informations sur la MT
Ta slovenski standard je istoveten z: CEN/TS 17466:2020
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST-TS CEN/TS 17466:2020 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST-TS CEN/TS 17466:2020
---------------------- Page: 2 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
May 2020
TECHNISCHE SPEZIFIKATION
ICS 03.220.20; 35.240.60
English Version
Intelligent transport systems - Urban ITS - Communication
interfaces and profiles for traffic management

Systèmes de transport intelligents - Systèmes de Intelligente Verkehrssysteme - Verkehrsmanagement-

gestion du trafic - Interfaces et informations sur la MT Systeme - TM-Schnittstellen und Informationen

This Technical Specification (CEN/TS) was approved by CEN on 28 March 2020 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to

submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS

available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in

parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,

Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,

Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and

United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels

© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 17466:2020 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466:2020 (E)
Contents Page

European foreword ....................................................................................................................................................... 4

Introduction .................................................................................................................................................................... 5

1 Scope .................................................................................................................................................................... 7

2 Normative references .................................................................................................................................... 7

3 Terms and definitions ................................................................................................................................... 8

4 Symbols and abbreviations ......................................................................................................................... 9

5 Traffic management interfaces ............................................................................................................... 11

5.1 Basics on traffic management .................................................................................................................. 11

5.2 Basics on interfaces ..................................................................................................................................... 11

5.3 Interactions between TM actors ............................................................................................................. 12

5.4 ITS-S Communication Profiles ................................................................................................................. 12

6 Use cases .......................................................................................................................................................... 12

6.1 Domains within traffic management .................................................................................................... 12

6.2 Operational activities ................................................................................................................................. 13

6.2.1 Overview ......................................................................................................................................................... 13

6.2.2 Status gathering ............................................................................................................................................ 14

6.2.3 Data retrieval ................................................................................................................................................. 14

6.2.4 Control .............................................................................................................................................................. 14

7 Data and communication protocols ...................................................................................................... 15

7.1 Data models .................................................................................................................................................... 15

7.1.1 DATEX II ........................................................................................................................................................... 15

7.1.2 OCIT-C ............................................................................................................................................................... 15

7.1.3 UTMC ................................................................................................................................................................. 17

7.1.4 DIASER.............................................................................................................................................................. 18

7.1.5 Other data models ........................................................................................................................................ 18

7.2 Mapping data models to communications protocols ...................................................................... 18

8 Application programming interfaces .................................................................................................... 19

8.1 Introduction ................................................................................................................................................... 19

8.2 Data exchange ............................................................................................................................................... 19

8.3 Filtering ........................................................................................................................................................... 19

8.4 Version management .................................................................................................................................. 20

8.5 Security mechanisms .................................................................................................................................. 20

8.6 ITS-S facilities ................................................................................................................................................ 20

8.6.1 HTTP ................................................................................................................................................................. 20

8.6.2 MQTT ................................................................................................................................................................ 20

8.6.3 AMQP ................................................................................................................................................................ 20

8.6.4 SOAP .................................................................................................................................................................. 20

8.6.5 RESTful ............................................................................................................................................................. 20

8.7 Communications features ......................................................................................................................... 21

9 Encodings ........................................................................................................................................................ 22

9.1 Interfaces using XML encoding ............................................................................................................... 22

9.1.1 Role .................................................................................................................................................................... 22

9.1.2 XML specification ......................................................................................................................................... 22

---------------------- Page: 4 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466:2020 (E)

9.2 Interfaces using JSON encoding ............................................................................................................... 22

9.2.1 Role .................................................................................................................................................................... 22

9.2.2 Relation to DATEX II implementations ................................................................................................. 23

9.2.3 JSON encoding for xsd data definitions ................................................................................................. 23

10 Communication interfaces, triple solutions and communication profiles .............................. 23

10.1 Concept of triple solutions ........................................................................................................................ 23

10.2 Triple solutions for traffic management .............................................................................................. 25

10.3 Communication protocol stacks .............................................................................................................. 25

10.4 Communication profile specifications .................................................................................................. 27

Annex A (informative) DATEX - JSON mapping ............................................................................................... 28

A.1 Initial developments in the DATEX group ........................................................................................... 28

A.2 JSON Schema definition mapping ............................................................................................................ 28

A.2.1 Introduction.................................................................................................................................................... 28

A.2.2 Mapping of “D2Datatype” .......................................................................................................................... 28

A.2.2.1 General ............................................................................................................................................................. 28

A.2.2.2 Mapping of datatypes table ....................................................................................................................... 29

A.2.2.3 Mapping of datatypes, schemaTypeInclude table ............................................................................. 30

A.2.3 Mapping of “D2Enumeration” and “D2Literal” .................................................................................. 31

A.2.4 Mapping of “D2Enumeration” and “D2Literal” .................................................................................. 32

A.2.5 Mapping of “D2Class” .................................................................................................................................. 33

A.2.5.1 General ............................................................................................................................................................. 33

A.2.5.2 “D2Class” classes without superclass .................................................................................................... 33

A.2.5.3 “D2Class” classes with superclass........................................................................................................... 35

A.2.5.4 “D2Class” classes which are superclasses............................................................................................ 36

A.2.6 Mapping of “D2Identifiable” and “D2VersionedIdentifiable” classes ........................................ 36

A.2.7 Root instances ................................................................................................................................................ 38

A.2.8 Extension mapping ....................................................................................................................................... 38

A.2.8.1 General ............................................................................................................................................................. 38

A.2.8.2 Extension mapping for Classes ................................................................................................................ 38

A.2.8.3 Extension mapping for Enumerations .................................................................................................. 39

A.2.9 Overall document structure and namespaces .................................................................................... 39

Bibliography ................................................................................................................................................................. 41

---------------------- Page: 5 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466:2020 (E)
European foreword

This document (CEN/TS 17466:2020) has been prepared by Technical Committee CEN/TC 278

“Intelligent transport systems”, the secretariat of which is held by NEN.

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. CEN shall not be held responsible for identifying any or all such patent rights.

This document has been prepared under a mandate given to CEN by the European Commission and the

European Free Trade Association.

According to the CEN/CENELEC Internal Regulations, the national standards organisations of the

following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria,

Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,

Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of

North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United

Kingdom.
---------------------- Page: 6 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466:2020 (E)
Introduction

General deployment of Intelligent Transport Systems (ITS) in the field of road transport and for interfaces

with other modes of transport is demanded by the Directive 2010/40/EU [3] of the European Parliament.

ITS means “applying information technology and communications technology (ICT) for improving traffic,

especially road traffic”.

Urban Intelligent Transport Systems (U-ITS) is a term indicating the provisioning of ITS services applying

ITS technologies in an urban context. Development of standards dedicated to U-ITS is supported by the

European Commission's mandate M/546 [2] with technical details identified in the final report [1] of

project team PT1701. U-ITS standards will complement those for cooperative ITS (C-ITS) developed

under the European Commission's mandate M/453, see [4].

NOTE Basic ITS technologies applied for U-ITS can be the same as those applied for C-ITS.

Provisioning of ITS services typically may require communications between ITS station units (ITS-SU)

specified in ISO 21217:2014. Diverging requirements for communications and limitations of capabilities

of available communication channels led to the concept of Hybrid Communications providing multiple

communication protocol stacks with different access technologies and communications protocols for

localized communications and networked communications together with the capability of handover,

specified in a series of standards, e.g. ISO 21217:2014, ISO 21218 [30], EN ISO 17423 [20], ISO 24102-6

[31], ISO 21215 [29], ISO 17515-3 [22], ISO 21210 [28], ISO 29281-1 [32], and others.

A major characteristic of C-ITS is the sharing of data between ITS applications in the same ITS-SU and in

different ITS-SUs. A major service domain of C-ITS is the domain of road safety and traffic efficiency, with

a certain focus on wireless communications between ITS-SUs installed in vehicles, also referred to as

Vehicle ITS-SU (V-ITS-SU), and wireless communications between V-ITS-SUs and ITS-SUs installed at the

roadside, also referred to as Roadside ITS-SU (R-ITS-SU).

Although there are differences between U-ITS and C-ITS with respect of target service domains (data and

procedures necessary for the provisioning of dedicated urban ITS services), data and procedures

developed for C-ITS might also be beneficially applied in U-ITS.

Whilst C-ITS currently largely focuses on the road safety domain, U-ITS deals with the ITS service

domains
— Multimodal Information Systems;
— Traffic Management;
— Urban Logistics;
see [1].

A major goal to be achieved with U-ITS standards is to assist urban administration to implement U-ITS,

and removing barriers for implementing U-ITS, see CEN/TR 17143 [1].

A precise definition of the borderline between U-ITS and ITS for other target domains, e.g. ITS on

highways, is impossible. However, this document aims on identifying and specifying ITS issues that are

relevant for urban administrations. It is important to understand that ITS issues developed for urban

areas also may be applicable outside of urban areas.

Development of standards for U-ITS has to consider automated and autonomous vehicles [1], and the

work on data and message specifications performed under the name of DATEX for data exchange between

central stations and between a central station and a service provider.

The present document was developed by project team PT1710 funded by the European Commission

under grant agreement SA/CEN/GROW/EFTA/546/2016-10 'Urban ITS Traffic Management data

---------------------- Page: 7 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466:2020 (E)

models' (M/546 [2]). The scope of the present document results from the High Level Recommendation

“1701-HLRd Traffic Management Data Models and interfaces” identified in CEN/TR 17143 [1].

The present document is about communications interfaces and profiles applicable for U-ITS with a focus

on communications between central stations, i.e. Central ITS-SUs (C-ITS-SUs). Such C-ITS-SUs can be part

of e.g. central traffic management centres, centres from authorities, centres from service providers. The

communication profile definitions presented in this document are based on the methodology being

specified in ISO/TS 21185.

Data definitions are outside the scope of this document and are developed within other PTs funded under

M/546 [2].
---------------------- Page: 8 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466:2020 (E)
1 Scope

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.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

ISO/TS 21177, Intelligent transport systems — ITS station security services for secure session establishment

and authentication between trusted devices

ISO/TS 21185, Intelligent transport systems — Communication profiles for secure connections between

trusted devices

ISO 21217:2014, Intelligent transport systems — Communications access for land mobiles (CALM) —

Architecture

EN 16157-1:2018, Intelligent transport systems — DATEX II data exchange specifications for traffic

management and information — Part 1: Context and framework
---------------------- Page: 9 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466:2020 (E)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https://www.iso.org/obp/ui
— IEC Electropedia: available at http://www.electropedia.org/
3.1
interface

point of demarcation between two entities through which information flows from one entity to the other

entity based on a given specification of technical details
3.2
logical interface

interface where the semantic, syntactic, and symbolic attributes of information flows is defined

3.3
physical interface

interface where the physical characteristics of signals used to represent information and the physical

characteristics of channels used to carry the signals are defined
3.4
service interface

interface where the set of interactions provided by an entity for participation with another entity for

some purpose along with constraints on how they can occur are defined
3.5
management service interface

service interface that exposes management functions of a service function contained in a component for

use by service consumers
[SOURCE: ISO 18202:2015, 1.4.7 - modified]
3.6
user interface

interface between a user and an interactive system that provides information and controls for the user

to accomplish specific tasks with the interactive system
[SOURCE: ISO/IEC 25063:2014, 3.18 - modified]
3.7
ITS service

functionality provided to users of intelligent transport systems designed e.g. to increase safety,

sustainability, efficiency, or comfort
[SOURCE: ISO 21217:2014, definition 3.11]
---------------------- Page: 10 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466:2020 (E)
3.8
ITS application

instantiation of an ITS service that involves an association of two or more complementary ITS-S

application processes
[SOURCE: ISO 21217:2014, definition 3.9]
3.9
ITS-S application process

element in an ITS station that performs information processing for a particular application and uses ITS-

S services to transmit and receive information
[SOURCE: ISO 21217:2014, definition 3.19]
3.10
ITS-S service

communication functionality of an ITS-S that provides the capability to connect to other nodes

[SOURCE: ISO 21217:2014, definition 3.37]
3.11
ITS station

functional entity comprised of an ITS-S facilities layer, ITS-S networking and transport layer, ITS-S access

layer, ITS-S management entity, ITS-S security entity, and ITS-S applications entity providing ITS services

Note 1 to entry: From an abstract point of view, the term “ITS station” refers to a set of functionalities. The term

is often used to refer to an instantiation of these functionalities in a physical unit. Often, the appropriate

interpretation is obvious from the context. The proper name of the physical instantiation of an ITS-S is ITS station

unit (ITS-SU).
[SOURCE: ISO 21217:2014, definition 3.12]
3.12
ITS-S-secured
secured in compliance with ISO 21217:2014
4 Symbols and abbreviations
AMQP advanced message queuing protocol
ANPR automatic number plate recognition
API application programming interface
ASN abstract syntax notation
CAM cooperative awareness message
CCTV closed circuit television
C-ITS cooperative ITS
C-ITS-SU central ITS-SU
DATEX data exchange
DENM decentralized environmental notification message
DIASER dialogue standard pour les équipements de régulation
---------------------- Page: 11 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466:2020 (E)
DSRC dedicated short range communications
NOTE 1 DSRC as specified in EN 12253 (5,8 GHz backscatter technology)

NOTE 2 In the United States of America, the term DSRC is used for IEEE 802.11 OCB

communications at 5,9 GHz. In order to distinguish both technologies, the US
understanding is referred to as US-DSRC.
DTS draft TS
EN European norm
EU European Union
HARTS harmonized architecture reference for technical standards
HTTP hypertext transfer protocol
ICT information and communication technology
IP Internet protocol
IPv6 IP version 6
IR infrared
ITS intelligent transport systems
ITS-S ITS station
ITS-SCP ITS-S communication profile
ITS-SCPS ITS-S communication protocol stack
ITS-SU ITS station unit
JSON Java script object notation
LAN local area network
LoS Level of Service
MQTT message queuing telemetry transport
NTCIP national transportation communications for ITS protocol
OCIT open communication interface for road traffic control systems
OCIT-C OCIT centre to centre
OCIT-O OCIT outstations
OID object identifier
PER packed encoding rules
PT project team
REST representational state transfer
RESTful REST implemented by using HTTP
RFC request for comments
SIRI service interface for real-time information
SNMP simple network management protocol
SOAP simple object access protocol
SPaT signal phase and timing
---------------------- Page: 12 ----------------------
SIST-TS CEN/TS 17466:2020
CEN/TS 17466:2020 (E)
TCP transmission control protocol
TM traffic management
TMC TM centre
TMDD TM data dictionary
TC technical committee
TLS transport layer security
TR technical report
TS technical specification
UML unified modelling language
UPER unaligned PER
URL uniform resource locator
UTC urban traffic control
UTMC urban traffic management and control
U-ITS urban ITS
VMS variable message sign
WG working group
WWW world wide web
XSD XML schema definition
XDR external data representation
XML extensible markup language
5 Traffic management interfaces
5.1 Basics on traffic management

“Traffic management” (TM), in the context of this document, is a term pointing to a class of ITS services

that aim on managing road traffic, including urban areas, including not just vehicles, motor-cycles, and

bicycles but also e.g. pedestrians and rail vehicles such as trams. TM interfaces exist between these actors

in TM. TM interfaces are needed for the purpose to manage the operation of TM services.

5.2 Basics on interfaces

The term “interface” has the generic meaning of a “point of demarcation between two entities”, although

originally it comes from natural science with a different meaning.

In the context of information and communications technologies (ICT), many complementary definitions

exist, distinguished by a qualifier added to the term, e.g. “physical interface”, “communications protocol

interface”, “application interface”. The communications protocol interface and the application interface

are examples of logical interfaces. The physical interface together with the communications protocol

interface define an ITS-S Communication Protocol Stack (ITS-SCPS).

NOTE 1 Typically, an ITS-SCPS includes, as a minimum, protocols from the ISO/OSI layers one through four (ITS-

S access layer and ITS-S networking and transport layer specified in ISO 21217:2014), optionally also the layers five

through seven (ITS-S facilities layer specified in ISO 21217:2014); see also the defini

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.