prEN 16157-1

SLOVENSKI STANDARD
01-september-2024
Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri
upravljanju prometa in informiranju - 1. del: Skladnost in okvir
Intelligent transport systems — DATEX II data exchange specifications for traffic
management and information — Part 1: Context and framework
Intelligente Verkehrssysteme - DATEX II Datenaustauschspezifikation für
Verkehrsmanagement und Verkehrsinformation - Teil 1: Kontext und Rahmenwerk
Systèmes de transport intelligents — Spécifications DATEX II d'échange de données
pour la gestion du trafic et l'information routière — Partie 1: Contexte et cadre général
Ta slovenski standard je istoveten z: prEN 16157-1
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

DRAFT
EUROPEAN STANDARD
NORME EUROPÉENNE
EUROPÄISCHE NORM
June 2024
ICS Will supersede EN 16157-1:2018
English Version
Intelligent transport systems - DATEX II data exchange
specifications for traffic management and information -
Part 1: Context and framework
Systèmes de transport intelligents - Spécifications Intelligente Verkehrssysteme - DATEX II
DATEX II d'échange de données pour la gestion du Datenaustauschspezifikation für Verkehrsmanagement
trafic et l'information routière - Partie 1: Contexte et und Verkehrsinformation - Teil 1: Kontext und
cadre général Rahmenwerk
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, Türkiye 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
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 16157-1:2024 E
worldwide for CEN national Members.

Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 6
3 Terms and definitions . 6
4 Symbols and abbreviations . 9
5 General conventions and requirements . 9
6 Platform independent model rules . 13
7 Extension rules . 24
Annex A (normative) XML Schema Definition Mapping . 26
Bibliography . 41

prEN 16156-1:2024 (E)
European foreword
This document (EN 16157-1:2024) 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 EN 16157-1:2017.
EN 16157-1:2024 includes the following significant technical changes with respect to EN 16157-1:2017:
• Introduction of a new stereotype for entities
• Introduction of a new stereotype for codelists
• New reference mechanism with graphical representation in UML
• Complex datatypes can be set as type of UML attributes
• Bugfixes and improvements of phrasing
EN 16157-1 is the first part of a multi-part standard under the general title “Intelligent transport systems
— DATEX II data exchange specifications for traffic management and information”.
This document has been prepared under a standardization request addressed to CEN by the European
Commission. The Standing Committee of the EFTA States subsequently approves these requests for its
Member States.
Introduction
This document defines a common set of data exchange specifications to support the vision of a seamless
interoperable exchange of road 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.
Deploying Intelligent Transport Systems in line with European Sustainable and Smart Mobility Strategy
in achieving connected and automated multimodal mobility as issued by the European Commission
requires co-ordination of traffic management operation and development of seamless pan European
information services. These jointly aim at contributing to the transformation of the European transport
system to the objectives of efficient, safe, sustainable, smart and resilient mobility.
In this context the European Commission has been supporting the development of information exchange
between the actors of the road traffic management - and related services- domain for a several 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 of the further evolution of the
standard and user support ecosystem. With this standardization of DATEX II, there is a real basis for
common exchange between the actors of the traffic and travel information sector both in the
collaboration between traffic management organisations and theirs systems, as well as in the coherent
way of information provision to service providers. DATEX II supports the requirements of the
stakeholder organisations involved in the road traffic and travel domain in compliance with the EU policy
and legal frameworks aimed at the sector.
The European Committee for Standardization (CEN) draws attention to the fact that it is claimed that
compliance with this document may involve the use of a patent concerning procedures, methods and/or
formats given in this document.
CEN takes no position concerning the evidence, validity and scope of patent rights.
This part of EN 16157 is targeted towards all stakeholders that want to understand the modelling
methodology applied throughout the DATEX II specifications. While this is potentially a wide range of
readers, the document addresses specifically those users that intend to extend the DATEX II data model
and therefore need to understand – and conform with – the modelling principles, the use of the Unified
Modelling Language (UML) and other conventions for DATEX II modelling.
Further to the UML modelling, this document also defines the mapping of this model to the eXtensible
Markup Language (XML), used for formatting data in DATEX II data exchanges. XML, being a widely used
method nowadays of formatting data for business-to-business data exchange over the Internet, is one of
the possible solutions for mapping the UML modelling into formatted data. Other methods like UPER
based on ASN.1 defined by ISO/IEC 8825-2 and JSON Schema defined by https://json-
schema.org/draft/2020-12/json-schema-core.html can also be considered and will potentially be
specified in further standards in this series. It should also be noted that this standard describes a
framework for DATEX II data that is usable for dynamic data messaging services. Other use cases like for
example map update exchange may benefit from other frameworks like e.g. Geography Markup Language
(GML). Thus, not all parts of the EN 16157 series will conform to all requirements of this document.
prEN 16156-1:2024 (E)
1 Scope
This document specifies and defines components required to support the exchange and shared use of
data and information in the field of traffic and travel.
The components include the framework and context for the modelling approach, data content, data
structure and relationships.
This document 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 document establishes specifications for data content to be exchanged between any two instances of
the following actors:
— Traffic Information Centres (TICs),
— Traffic Control Centres (TCCs),
— Service Providers (SPs),
Use of this document may be applicable for use by other actors.
The 16157 series of European Standards cover, 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,
— Information about operator initiated actions – including both advisory and mandatory measures,
— 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 information and advice relating to use of the road network.
— Traffic Regulations
This part of EN 16157 specifies the DATEX II framework of all parts of this document, the context of use
and the modelling approach taken and used throughout these European Standards. This approach is
described using formal methods and provides the mandatory reference framework for all other parts.
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/IEC 19505-1:2012, Information technology — Object Management Group Unified Modeling Language
(OMG UML) — Part 1: Infrastructure
ISO/IEC 14977:1996, Information technology — Syntactic metalanguage — Extended BNF
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp/
— IEC Electropedia: available at https://www.electropedia.org/
NOTE Some Definitions in this clause have been taken from ISO/IEC 19505-1:2012 but have been adapted to
meet the particular use of UML within this specification.
3.1
association
semantic relationship between classes
3.2
attribute
named slot within a class that describes a range of values that instances of the class may hold
3.3
class
description of a set of objects that share the same attributes, relationships, and semantics
3.4
composition
association between two classes, where one class is a composite and the other is a part
Note 1 to entry: This characteristic is expressed in UML with an attribute named “isComposite” on the part end of
the Association being set to “true”.
3.5
dependency
implementation or functioning of one or more elements that requires the presence of one or more other
elements
3.6
enumeration
data type whose range is a list of predefined values, called enumeration literals
3.7
enumeration literal
element of the value space of an enumeration data type
prEN 16156-1:2024 (E)
3.8
generalization
taxonomic relationship between a more general element and a more specific element
3.9
multiplicity
range of integers specifying the allowable cardinalities for an instantiation of an element
Note 1 to entry: The upper bound of the range cannot be below the lower bound. The lower bound is a nonnegative
integer. The upper bound is a nonnegative integer or the special value unlimited, which indicates there is no upper
bound on the range.
3.1
...