kSIST FprEN 16157-4:2020

Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 4: VMS publication

This European Standard (EN 16157 series) specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.
This European Standard is applicable to:
-   Traffic and travel information which is of relevance to road networks (non-urban and urban),
-   Public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service),
-   Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This European Standard establishes specifications for data exchange between any two instances of the following actors:
-   Traffic Information Centres (TICs),
-   Traffic Control Centres (TCCs),
-   Service Providers (SPs),
Use of this European Standard may be applicable for use by other actors.
This European Standard series covers, at least, the following types of informational content:
-   Road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment,
-   Operator initiated actions,
-   Road traffic measurement data, status data, and travel time data,
-   Travel information relevant to road users, including weather and environmental information,
-   Road traffic management information and instructions relating to use of the road network.
This part of the CEN/TS 16157 series specifies the informational structures, relationships, roles, attributes and associated data types required for publishing variable message sign information within the Datex II framework. This is specified in two publications, a DATEX II VMS Table Publication sub-model and a VMS Publication sub-model, which are part of the DATEX II platform independent model, but this part excludes those elements that relate to:
-   location information which are specified in EN 16157-2,
-   common information elements, which are specified in EN 16157-7,
-   situation information which are specified in EN 16157-3.
The VMS Table Publication supports the occasional exchange of tables containing generally static reference information about deployed VMS which enable subsequent efficient references to be made to pre-defined static information relating to those VMS. The VMS Publication supports the exchange of the graphic and textual content of one or several VMS plus any status information on device configuration that aid the comprehension of the informational content. This content is potentially subject to rapid change.
These publications are not intended to support the control or configuration of VMS equipment. Each is part of the DATEX II platform independent model.

Intelligente Transportsysteme - DATEX II Datenaustausch Spezifikationen für Verkehrsmanagement und Verkehrsinformation - Teil 4: Veröffentlichungen Variable Verkehrszeichen (VMS)

Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri upravljanju prometa in informiranju - 4. del: Objava informacij o znakih s spremenljivim sporočilom (VMS)

Standards Content (sample)

SLOVENSKI STANDARD
oSIST prEN 16157-4:2019
01-december-2019

Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri

upravljanju prometa in informiranju - 4. del: Objava informacij o znakih s
spremenljivim sporočilom (VMS)

Intelligent transport systems - DATEX II data exchange specifications for traffic

management and information - Part 4: VMS publication
Intelligente Transportsysteme - DATEX II Datenaustausch Spezifikationen für
Verkehrsmanagement und Verkehrsinformation - Teil 4: Veröffentlichungen Variable
Verkehrszeichen (VMS)
Ta slovenski standard je istoveten z: prEN 16157-4
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
oSIST prEN 16157-4:2019 en,fr,de

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

---------------------- Page: 1 ----------------------
oSIST prEN 16157-4:2019
---------------------- Page: 2 ----------------------
oSIST prEN 16157-4:2019
DRAFT
EUROPEAN STANDARD
prEN 16157-4
NORME EUROPÉENNE
EUROPÄISCHE NORM
October 2019
ICS 35.240.60 Will supersede CEN/TS 16157-4:2014
English Version
Intelligent transport systems - DATEX II data exchange
specifications for traffic management and information -
Part 4: VMS publication
Intelligente Verkehrssysteme - DATEX II
Datenaustausch Spezifikation für
Verkehrsmanagement und Information - Teil 4:
Veröffentlichungen Variable Verkehrszeichen (VMS)

This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee

CEN/TC 278.

If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations

which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.

This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other

language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC

Management Centre has the same status as the official versions.

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.

Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are

aware and to provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without

notice and shall not be referred to as a European Standard.
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

© 2019 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 16157-4:2019 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 16157-4:2019
prEN 16157-4:2019 (E)
Contents Page

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

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

1 Scope .................................................................................................................................................................... 6

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

3 Terms and definitions ................................................................................................................................... 7

4 Symbols and abbreviations ......................................................................................................................... 8

5 Conformance ..................................................................................................................................................... 8

6 UML notation .................................................................................................................................................... 8

7 The VMS model ................................................................................................................................................. 9

7.1 Overview of the VMS model ......................................................................................................................... 9

7.2 The VMS Table Publication model ............................................................................................................ 9

7.3 The VMS Table Publication package ........................................................................................................ 9

7.3.1 Overview of the VMS Table Publication package ................................................................................. 9

7.3.2 Semantics of the VMS Table Publication package ............................................................................ 10

7.4 The VMS Publication model ...................................................................................................................... 12

7.5 The VMS Publication package .................................................................................................................. 12

7.5.1 Overview of the VMS Publication package .......................................................................................... 12

7.5.2 Semantics of the VMS Publication package ......................................................................................... 13

7.6 The Fault Package ........................................................................................................................................ 14

7.6.1 Overview of the Fault package ................................................................................................................ 14

7.6.2 Semantics of the Fault Publication package ....................................................................................... 14

7.7 The Graphic Data Dictionary package .................................................................................................. 15

7.7.1 Overview of the Graphic Data Dictionary package .......................................................................... 15

7.7.2 Semantics of the Graphic Data Dictionary package ......................................................................... 15

7.8 The Vms Status package ............................................................................................................................ 16

7.8.1 Overview of the Vms Status package ..................................................................................................... 16

7.8.2 Semantics of the VMS Status package ................................................................................................... 18

7.9 The Vms Message package ........................................................................................................................ 20

7.9.1 Overview of the Vms Message package ................................................................................................ 20

7.9.2 Semantics of the VMS Message package ............................................................................................... 21

Annex A (normative) Data Dictionary ................................................................................................................. 24

A.1 Overview ......................................................................................................................................................... 24

A.2 Data Dictionary for “VMS” ......................................................................................................................... 25

A.2.1 “Classes” package ......................................................................................................................................... 25

A.2.2 “Fault” package ............................................................................................................................................. 28

A.2.3 “GraphicDataDictionary” package ......................................................................................................... 29

A.2.4 “VmsMessage” package .............................................................................................................................. 31

A.2.5 “VmsPublication” package ........................................................................................................................ 39

A.2.6 “VmsRelated” package ................................................................................................................................ 39

A.2.7 “VmsStatus” package ................................................................................................................................... 44

A.2.8 “VmsTablePublication” package ............................................................................................................. 49

A.3 Data Dictionary of <> for “VMS” ................................................................................. 50

A.3.1 Introduction ................................................................................................................................................... 50

---------------------- Page: 4 ----------------------
oSIST prEN 16157-4:2019
prEN 16157-4:2019 (E)

A.3.2 The <> “GddPictogramCategoryCode” ..................................................................... 50

A.4 Data Dictionary of<> for “VMS” .......................................................................... 50

A.4.1 Introduction.................................................................................................................................................... 50

A.4.2 The <> "CodedReasonForSettingMessageEnum” ......................................... 50

A.4.3 The <> “ColourEnum” ............................................................................................. 51

A.4.4 The <> “GddServiceCategory” ............................................................................. 51

A.4.5 The <> “ImageFormatEnum” ............................................................................... 52

A.4.6 The <> “PhysicalMountingEnum” ...................................................................... 52

A.4.7 The <> “PositionAbsoluteEnum” ........................................................................ 52

A.4.8 The <> “PositionRelativeEnum” ......................................................................... 53

A.4.9 The <> “VmsDatexPictogramEnum” ................................................................. 53

A.4.10 The <> “VmsDatexSupplementalPictogramEnum” ..................................... 55

A.4.11 The <> “VmsFaultEnum” ....................................................................................... 57

A.4.12 The <> “VmsLuminanceLevelEnum” ................................................................ 58

A.4.13 The <> “VmsMessageInformationTypeEnum” .............................................. 59

A.4.14 The <> “VmsTypeEnum” ....................................................................................... 60

Annex B (normative) Referenced XML Schema for Vms related Publications ...................................... 61

B.1 Overview .......................................................................................................................................................... 61

B.2 Schema .............................................................................................................................................................. 61

Bibliography ................................................................................................................................................................. 77

---------------------- Page: 5 ----------------------
oSIST prEN 16157-4:2019
prEN 16157-4:2019 (E)
European foreword

This document (prEN 16157-4:2019) has been prepared by Technical Committee CEN/TC 278

“Intelligent transport systems”, the secretariat of which is held by NEN.
This document is currently submitted to the CEN Enquiry.
This document will supersede CEN/TS 16157-4:2014.

The major differences introduced in the new edition of this part are the following:

— renaming of some major classes (e.g. currently renamed Vms, VmsUnit, VmsUnitStatus, VmsStatus)

to improve the understanding and the usage of the modelled information;

— compliance to EN ISO 14823, Intelligent transport systems – Graphic data dictionary (ISO 14823), for

description of Pictogram graphical information;
— correction of different bugs.

prEN 16157-4 is the fourth part of a multi-part standard under the general title Intelligent transport

systems – DATEX II data exchange specifications for traffic management and information, the other parts

are:
— Part 1: Context and framework;
— Part 2: Location referencing;
— Part 3: Situation Publication;
— Part 5: Measured and elaborated data publications [CEN/TS];
— Part 6: Parking Publications [CEN/TS];
— Part 7: Common data elements;

— Part 8: Traffic management publications and extensions dedicated to the urban environment

[FprCEN/TS];

— Part 9: Traffic signal management publications dedicated to the urban environment [FprCEN/TS].

Other parts will be developed in the future.
---------------------- Page: 6 ----------------------
oSIST prEN 16157-4:2019
prEN 16157-4:2019 (E)
Introduction

This European Standard defines a common set of data exchange specifications to support the vision of a

seamless interoperable exchange of traffic and travel information across boundaries, including national,

urban, interurban, road administrations, infrastructure providers and service providers.

Standardization in this context is a vital constituent to ensure interoperability, reduction of risk,

reduction of the cost base, promotion of open marketplaces and many social, economic and community

benefits to be gained from more informed travellers, network managers and transport operators.

Delivering European Transport Policy in line with the White Paper issued by the European Commission

requires co-ordination of traffic management and development of seamless pan European services.

With the aim to support sustainable mobility in Europe, the European Commission has been supporting

the development of information exchange mainly between the actors of the road traffic management

domain for a number of years. In the road sector, DATEX II has been long in fruition, with the European

Commission being fundamental to its development through an initial contract and subsequent co-

funding through the Euro-Regional projects. With this standardization of DATEX II, there is a real basis

for common exchange between the actors of the traffic and travel information sector.

This European Standard includes the framework and context for exchanges, the modelling approach,

data content, data structure and relationships.
This European Standard supports a methodology that is extensible.

The fourth part of this European Standard deals with the publication of variable message sign (VMS)

information. It specifies the structures and definitions of information that can be exchanged to convey

details of the messages displayed on variable message signs, and the current configuration and

characteristics and status of the variable message signs that are currently deployed on the road

network.
---------------------- Page: 7 ----------------------
oSIST prEN 16157-4:2019
prEN 16157-4:2019 (E)
1 Scope

This European Standard (EN 16157 series) specifies and defines component facets supporting the

exchange and shared use of data and information in the field of traffic and travel.

The component facets include the framework and context for exchanges, the modelling approach, data

content, data structure and relationships.
This European Standard is applicable to:

— Traffic and travel information which is of relevance to road networks (non-urban and urban),

— Public transport information that is of direct relevance to the use of a road network (e.g. road link

via train or ferry service),

— Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).

This European Standard establishes specifications for data exchange between any two instances of the

following actors:
— Traffic Information Centres (TICs),
— Traffic Control Centres (TCCs),
— Service Providers (SPs),
Use of this European Standard may be applicable for use by other actors.

This European Standard series covers, at least, the following types of informational content:

— Road traffic event information – planned and unplanned occurrences both on the road network and

in the surrounding environment,
— Operator initiated actions,
— Road traffic measurement data, status data, and travel time data,

— Travel information relevant to road users, including weather and environmental information,

— Road traffic management information and instructions relating to use of the road network.

This part of the CEN/TS 16157 series specifies the informational structures, relationships, roles,

attributes and associated data types required for publishing variable message sign information within

the Datex II framework. This is specified in two publications, a DATEX II VMS Table Publication sub-

model and a VMS Publication sub-model, which are part of the DATEX II platform independent model,

but this part excludes those elements that relate to:
— location information which are specified in EN 16157-2,
— common information elements, which are specified in EN 16157-7,
— situation information which are specified in EN 16157-3.

The VMS Table Publication supports the occasional exchange of tables containing generally static

reference information about deployed VMS which enable subsequent efficient references to be made to

pre-defined static information relating to those VMS. The VMS Publication supports the exchange of the

graphic and textual content of one or several VMS plus any status information on device configuration

---------------------- Page: 8 ----------------------
oSIST prEN 16157-4:2019
prEN 16157-4:2019 (E)

that aid the comprehension of the informational content. This content is potentially subject to rapid

change.

These publications are not intended to support the control or configuration of VMS equipment. Each is

part of the DATEX II platform independent model.
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.

EN 16157-1, Intelligent transport systems – DATEX II data exchange specifications for traffic management

and information – Part 1: Context and framework

EN 16157-2, Intelligent transport systems – DATEX II data exchange specifications for traffic management

and information – Part 2: Location referencing

EN 16157-7, Intelligent transport systems – DATEX II data exchange specifications for traffic management

and information – Part 7: Common data elements

EN ISO 14823, Intelligent transport systems – Graphic data dictionary (ISO 14823)

3 Terms and definitions

For the purposes of this document, the terms and definitions given in EN 16157-1, EN 16157-2 and the

following apply.

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

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

representation of a graphic symbol displayed on a variable message sign by means of a (usually multi

colour capable) matrix or LED display panel
3.2
supplementary panel

additional display panel, either physically separate or integrated with the main display panel which can

display information or regulatory instructions which are supplemental to the associated pictogram,

comprising either an additional line of text or a pictogram or both
3.3
variable message sign

sign/display panel used for the purpose of displaying one or more messages (comprising any

combination of textual, symbol or pictogram information) that can be changed or switched on or off as

required
3.4
variable message sign unit

roadside unit which can control one or more variable message signs on a single gantry/mounting or on

closely associated separate gantries/mountings
---------------------- Page: 9 ----------------------
oSIST prEN 16157-4:2019
prEN 16157-4:2019 (E)
4 Symbols and abbreviations

For the purposes of this document, the abbreviation of terms given in EN 16157-1 and the following

apply.
IP Internet Protocol
UML Unified Modelling Language
URL Uniform Resource Locator
VMS Variable Message Sign
5 Conformance

This document specifies a DATEX II VMS unit table publication and a DATEX II VMS status publication,

except for these elements that relate to location information which are specified in EN 16157-2 or for

the common elements (i.e. shared between several publications) which are defined in EN 16157-7.

The DATEX II platform independent data model, of which these two publication sub-models are a part,

corresponds to the level A model as defined in EN 16157-1.

Conformance with this document shall require platform independent models from which platform

specific models are generated to comply with the UML modelling rules defined in EN 16157-1 and with

the following requirements of the sub-models which are expressed in this document:

— comply with all stipulated minimum and maximum multiplicity requirements for UML elements

and relationships;
— comply with all definitions, types and ordering;
— employ optional elements as specified;
— comply with all expressed constraints.

It should be noted that conformance of a publication service with all the structural requirements stated

above does not necessarily ensure that the informational content of that service will be semantically

comprehensible.

Conformance with this Part shall require platform independent models from which platform specific

models are generated to comply with the UML modelling rules defined in EN 16157-1 and with the

following requirements of this sub-model which are expressed in this part.

It should be noted that conformance of a publication service with all the structural requirements stated

above does not necessarily ensure that the informational content of that service will be semantically

comprehensible.
6 UML notation

The UML notation used in EN 16157 (all parts) complies with ISO/IEC 19505-1. A short summary

explaining the notation used in this document is provided in EN 16157-1:2018, Annex A.

---------------------- Page: 10 ----------------------
oSIST prEN 16157-4:2019
prEN 16157-4:2019 (E)
7 The VMS model
7.1 Overview of the VMS model

The VMS model shall be immediately subordinate to the “PayloadPublication” package and shall

comprise the packages used in the VMS Table Publication and VMS Publication and the Classes and

Enumerations specific for these Payload Publication.

Some of the packages and individual classes used within the “VMS Model” package reside in the

“D2Namespace” namespaces “Common”, “Location”, “SituationPublication” and because they can be

used in different places within this package or by other packages either now or in the future. The named

namespaces (D2Namespace) shall be a container for a number of packages and individual reusable

classes. Those packages and classes which are contained in the named namespaces are identified in the

following clauses. The use of individual classes from the named namespace is only described in detail if

their use in the “VMS Publication” affects their semantics.

The classes, attributes, data types and enumerations that are specific to this document are defined in

the normative Annex A.

The XML subschema corresponding to this document is provided in the normative Annex B.

7.2 The VMS Table Publication model

The VMS Table Publication model shall comprise a top-level package, “VmsTablePublication” which

utilizes some classes from the “Classes” package.

The “VmsTablePublication” package shall model the normally static characteristics of VMS units and

their controlled VMS.

Each “VmsTablePublication” instance shall contain one or more instances of a “VmsUnitTable”, each

table containing a number of “VmsUnits” which relate to deployed VMS units. Each “VmsUnit” shall

contain one or more “Vmss” each of which relates to a specific VMS that is controlled by the VMS unit.

Although the characteristics of VMSs and VMS units modelled in this publication are normally static,

sometimes these characteristics change over a period of time. For instance, changes do occur in the

location of VMSs when they are of a mobile type or in the number of lines of text if the sign supports

variable font sizes. In these cases, some of the characteristics defined in this publication may be

overridden by more up-to-date information promulgated in a “VmsPublication”. VMS characteristics

information provided in a “VmsPublication” shall always override any characteristics information

provided in the records of a “VmsTablePublication”.
7.3 The VMS Table Publication package
7.3.1 Overview of the VMS Table Publication package

The “VmsTablePublication” package shall comprise a sub-model for defining information describing the

normally static characteristics of VMS units and their VMS (see Figure 1). Each publication may contain

one or more tables, allowing logical partitioning of VMS static information as deemed most appropriate

for recipients of VMS information by the supplier (e.g. by road designation or other geographic criteria

or by type of VMS equipment etc.).
The VMS Table class diagram is shown in Figure 1.
---------------------- Page: 11 ----------------------
oSIST prEN 16157-4:2019
prEN 16157-4:2019 (E)
Figure 1 — The “VmsTablePublication” package class model
7.3.2 Semantics of the VMS Table Publication package
7.3.2.1 “VmsTablePublication” package semantics - general

The “VmsTablePublication” class shall be a specific realizable class as specialization of

“PayloadPublication”. Each “VmsTablePublication” may contain any number of separate VMS Unit

Tables.

The information in the “VmsTablePublication” shall relate to the VMS units and their controlled VMSs

currently deployed on the road, and shall contain the normally static characteristics of those devices at

a specified point in time. However, the characteristics of any VMS given in the “VmsTablePublication”

shall be overridden by any corresponding characteristics that are given in a “VmsPublication” for the

same VMS.
---------------------- Page: 12 ----------------------
oSIST prEN 16157-4:2019
prEN 16157-4:2019 (E)

Some of the individual classes used within the “VmsTablePublication” package, principally those for

modelling the characteristics of a VMS, also reside in the “VmsRelated” package which is within the

“Classes” package as they are also used in the “VmsPublication” package”.
7.3.2.2 “VmsTablePublication” Class

The “VmsTablePublication” class shall be the base class for containing the published VMS unit tables.

7.3.2.3 “HeaderInformation” Class

Each instance of a “VmsTablePublication” shall have associated metadata contained in an instance of

the “HeaderInformation” class which shall allow the supplier of the “VmsTablePublication” to specify

how the recipient should treat the information contained in it. For “HeaderInformation” class refer to

EN 16157-7.
7.3.2.4 “VmsUnitTable” Class

An identifiable versioned instance of the “VmsUnitTable” class shall contain any logical collection of

“VmsUnitRecords”. A supplier may choose to provide a textual identifier for a particular

“VmsUnitTable” to clarify the logical collection of “VmsUnit”.
7.3.2.5 “VmsUnit” Class

An identifiable versioned instance of the “VmsUnit” class shall contain the characteristics information

relating to a specific VMS unit. Each record shall have one or more indexed “Vms” sub-records for

containing the characteristics of the individual VMSs that are controlled by the VMS unit. The

“vmsIndex” qualifier allows the specific VMS that is controlled by the VMS unit to be specified.

7.3.2.6 “Vms” Class

An instance of the “Vms” class shall allow a supplier to identify the normally static characteristics of a

VMS. The location of the VMS may be specified via the composition to “vmsLocation” and any location

that is managed by the VMS such as a car park or junction may be specified via composition with the

“VmsManagedLogicalLocation” class.
The LocationReference class sha
...