ISO/TS 19468:2022

Intelligent transport systems - Data interfaces between centres for transport information and control systems - Platform-independent model specifications for data exchange protocols for transport information and control systems

This document defines and specifies component facets supporting the exchange and shared usage of data and information in the field of traffic and travel. The component facets include the framework and context for exchanges, the data content, structure and relationships necessary and the communications specifications, in such a way that they are independent from any defined technical platform. This document establishes specifications for data exchange between any two instances of the following actors: - Traffic information centres (TICs); - Traffic control centres/Traffic management centres (TCCs/TMCs); - Service providers (SPs). This document can also be applied for use by other actors, e.g. car park operators. This document includes the following types of information: - use cases and associated requirements, and features relative to different exchange situations; - different functional exchange profiles; - abstract elements for protocols; - data model for exchange (informational structures, relationships, roles, attributes and associated data types required). In order to set up a new technical exchange framework, it is necessary to associate one functional exchange profile with a technical platform providing an interoperability domain where plug-and-play interoperability at a technical level can be expected. The definition of such interoperability domains is out of scope of this document but can be found in other International Standards or Technical Specifications (e.g. the ISO 14827 series). This document is restricted to data exchange. Definition of payload content models is out of the scope of this document.

Systèmes de transport intelligents — Interface de données entre centres pour les systèmes de commande et d'information des transports — Spécification du modèle indépendant de plateforme pour les protocoles d'échange de données pour les systèmes de commande et d'information des transports

General Information

• Status: Published
• Publication Date: 13-Feb-2022
• ICS: 03.220.20 - Road transport
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204/WG 9 - Integrated transport information, management and control
• Current Stage: 9092 - International Standard to be revised
• Start Date: 10-Nov-2025
• Completion Date: 13-Dec-2025

Relations

• Consolidates: ISO 21846:2018 - Vegetable fats and oils - Determination of composition of triacylglycerols and composition and content of diacylglycerols by capillary gas chromatography
• Effective Date: 06-Jun-2022
• Revises: ISO/TS 19468:2019 - Intelligent transport systems - Data interfaces between centres for transport information and control systems - Platform independent model specifications for data exchange protocols for transport information and control systems
• Effective Date: 08-May-2020

Overview

ISO/TS 19468:2022 - Intelligent transport systems - Platform-independent model specifications for data exchange protocols - defines a platform-independent framework for exchanging and sharing data among centres that manage transport information and control. The Technical Specification focuses on the component facets required for data exchange between Traffic Information Centres (TICs), Traffic Control / Traffic Management Centres (TCCs/TMCs) and Service Providers (SPs) (and can be applied to other actors such as car park operators). ISO/TS 19468:2022 is restricted to data exchange modeling and does not define payload content models or the technical interoperability domains themselves.

Key topics and technical requirements

• Platform-independent models (PIMs): Abstract protocol elements and UML-based modeling for exchange patterns so implementations can be mapped to different technical platforms.
• Exchange modeling framework: Business scenarios, functional exchange profiles, requirements, features and exchange patterns (e.g., snapshot pull, snapshot push, simple push, stateful push, simple CIS).
• Exchange data model: Informational structures, relationships, roles, attributes and associated data types required for exchanges.
• Exchange features: Subscription contracts, session management, information management, data delivery semantics, self-description and communication considerations.
• Use cases and requirements: Scenarios and feature sets tailored to different exchange situations and service types.
• Abstract elements for protocols: Message definitions and state diagrams to support consistent implementations.
• Constraints: Definition of interoperability domains (plug-and-play technical interoperability) and payload content models are out of scope; see related standards (for example, the ISO 14827 series) for technical platform definitions.

Practical applications and who uses it

ISO/TS 19468:2022 is practical for organizations designing interoperable ITS data exchanges:

• Traffic authorities and TMCs/TICs implementing standardized interfaces for sharing situational data and control messages.
• Service providers (map, traffic, fleet management, parking) integrating with centre-to-centre data interfaces.
• System architects and integrators creating protocol mappings from PIMs to concrete technical platforms (HTTP/REST, MQTT, DATEX II bindings, etc.).
• Vendors and platform developers who need UML-based models and exchange patterns to ensure consistent behavior across deployments.

Benefits include clearer data interface design, reduced integration effort, and a blueprint to achieve interoperable transport information and control systems when PIMs are bound to a chosen technical platform.

Related standards

• ISO 14827 series (examples of defining interoperability domains and technical protocol bindings).
• Other ITS standards and specifications for payload/content models (payload definitions are outside ISO/TS 19468:2022 scope).

Keywords: ISO/TS 19468:2022, intelligent transport systems, data interfaces, data exchange protocols, platform-independent model, TIC, TMC, traffic information, traffic control, exchange patterns, interoperability.

Standards Content (Sample)

TECHNICAL ISO/TS
SPECIFICATION 19468
Second edition
2022-02
Intelligent transport systems —
Data interfaces between centres for
transport information and control
systems — Platform-independent
model specifications for data exchange
protocols for transport information
and control systems
Systèmes de transport intelligents — Interface de données entre
centres pour les systèmes de commande et d'information des
transports — Spécification du modèle indépendant de plateforme
pour les protocoles d'échange de données pour les systèmes de
commande et d'information des transports
Reference number
© ISO 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword . vi
Introduction .viii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms.4
5 Exchange modeling framework .5
5.1 Overview . 5
5.2 Business scenarios and functional exchange profiles . 5
5.3 Requirements, features and exchange patterns . 6
5.4 Business scenario: information delivery . 7
5.4.1 Overview . 7
5.4.2 Requirements . 9
5.4.3 Data delivery exchange pattern . 9
5.4.4 Specific exchange pattern specification PIMs included in this document . 9
5.5 Business scenario: collaborative ITS services . 9
5.5.1 Overview . 9
5.5.2 Data exchange-enabling service request and feedback paradigm . 10
5.5.3 Requirements . 11
5.6 Exchange data model . 11
5.7 Data exchange features . 11
5.7.1 Context diagram . 11
5.7.2 Features . 12
5.8 Exchange pattern modeling using UML . 16
6 Snapshot pull .20
6.1 Overview . 20
6.2 Exchange pattern messages definition . 21
6.2.1 Overall presentation . 21
6.2.2 Exchange pattern definition . 22
6.2.3 Relevant exchange information in exchange data model .23
6.2.4 Exchange messages . 23
6.3 State diagrams .23
6.4 Features implementation description . 23
6.4.1 Overview .23
6.4.2 Subscription contract . 24
6.4.3 Session . 24
6.4.4 Information management. 24
6.4.5 Data delivery . 25
6.4.6 Self-description . 27
6.4.7 Communication. 27
6.4.8 General optimization issues . 27
7 Snapshot push .27
7.1 Overview . 27
7.2 Exchange pattern messages definition .28
7.2.1 Overall presentation .28
7.2.2 Basic exchange pattern . .28
7.2.3 Relevant exchange information in exchange data model .29
7.2.4 Exchanged messages .30
7.3 State diagrams .30
7.4 Features implementation description .30
7.4.1 Subscription contract . 31
7.4.2 Session . 31
iii
7.4.3 Information management. 31
7.4.4 Data delivery . 31
7.4.5 Self-description . 33
7.4.6 Communication/protocol . 33
7.4.7 General optimization issues . 33
8 Simple push . .33
8.1 Overview . 33
8.2 Exchange pattern messages definition .34
8.2.1 Overall presentation .34
8.2.2 Basic exchange pattern . 35
8.2.3 Relevant exchange information from exchange data model .36
8.2.4 List of exchanged messages . 37
8.3 State diagrams .38
8.4 Features implementation description .40
8.4.1 Overview .40
8.4.2 Subscription contract .40
8.4.3 Session .40
8.4.4 Information management. 42
8.4.5 Data delivery . 42
8.4.6 Self-description . 43
8.4.7 Communication/protocol . 43
8.4.8 General optimization issues . 43
9 Stateful push .43
9.1 Overview . 43
9.2 Exchange pattern messages definition .44
9.2.1 Overall presentation .44
9.2.2 Basic exchange pattern . . 45
9.2.3 Relevant exchange information from exchange data model . 47
9.2.4 List of exchanged messages .48
9.3 State Diagrams .48
9.4 Features implementation description .50
9.4.1 Overview . 50
9.4.2 Subscription contract . 51
9.4.3 Session . 51
9.4.4 Information management. 53
9.4.5 Data delivery . 53
9.4.6 Self-description .54
9.4.7 Communication.54
9.4.8 General optimization issues .54
10 Simple CIS .55
10.1 Overview . 55
10.2 Exchange pattern and messages definition . 55
10.2.1 Overall presentation . 55
10.2.2 Basic exchange pattern . .56
10.2.3 Relevant exchange information from exchange data model .58
10.2.4 Exchanged messages . 59
10.3 State diagrams .60
10.4 Features implementation description . 61
10.4.1 Overview . 61
10.4.2 Subscription contract . 61
10.4.3 Session . 61
10.4.4 Information management. 61
10.4.5 Self-description .66
10.4.6 Communication/protocol .66
11 Stateful CIS .66
11.1 Overview .66
iv
11.2 Exchange pattern and messages definition . 67
11.2.1 Overall presentation . 67
11.2.2 Basic exchange pattern .68
11.2.3 Relevant exchange information from exchange data model . 70
11.2.4 Exchanged messages . 71
11.3 State diagrams .73
11.4 Features implementation description .74
11.4.1 Overview .74
11.4.2 Subscription contract . 75
11.4.3 Session . 75
11.4.4 Information management. 75
11.4.5 Self-description . 76
11.4.6 Communication. 76
12 Other PIM definitions .76
Annex A (informative) Methodology presentation .77
Annex B (normative) Definition of requirements .79
Annex C (normative) Basic exchange data model and data dictionary .84
Annex D (informative) Introduction to communications and protocols .117
Annex E (informative) Major functional exchange profile and exchange patterns for
information delivery. 122
Annex F (informative) Data delivery background: stateless and stateful information with
information life cycle management .124
Annex G (informative) Collaborative ITS services (CIS) background . 126
Bibliography . 139
v
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems, in
collaboration with the European Committee for Standardization (CEN) Technical Committee CEN/TC
278, Intelligent transport systems, in accordance with the Agreement on technical cooperation between
ISO and CEN (Vienna Agreement).
This second edition cancels and replaces the first edition (ISO/TS 19468:2019), which has been
technically revised.
The main changes are as follows:
— UML Communication diagrams have been improved (introduction of Agents and Interfaces to define
actor subsystems interactions and addition of subclause 5.8 to describe UML modeling methodology
adopted);
— Void input parameter has been defined;
— Description of FEP+EP implementation has been improved with appropriate normative language;
— Publish Subscrube Exchange Pattern has been removed;
— Collaborative Intellignet Transport Systems (ITS) services requirements and features have been
reviewed and added in Clause 5 and Annexes B and E;
— Collaborative ITS service FEP+EP PIM description has been introduced in Clauses 10 and 11;
— Annex C has been reviewed, introducing new classes and attributes to support the implementation
of features used in other exchange patterns;
— Annex H has been deleted;
— Certain figures have been improved.
vi
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
vii
Introduction
This document 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.
[13]
Especially in Europe, delivering 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 of supporting 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.
This document supports a methodology that is extensible.
To be able to successfully connect systems and start exchanging data in an interoperable and easy
way, there is a need to describe and agree on how this exchange ought to be achieved. This is set out
in a data exchange specification. Data exchanges in different scenarios can have different needs and
requirements. Therefore, several data exchange specifications can be needed.
Data exchange specifications need to address two main issues. Firstly, they model the stakeholders
and actors involved in data exchange, each potentially in different roles, as well as abstract exchange
patterns for their interactions. Secondly, they select a suitable implementation platform and clearly
specify how the abstract scenarios and patterns are effectively implemented on this platform.
The diagram in Figure 1 shows such an abstract communication scenario from the perspective of a
road operator who requires data exchange interfaces between the different components of its own
operational systems, either between centre-side components or between centre and field devices, but
also to exchange information with other road operators or service providers.
Figure 1 — Abstract communication scenario
While the black links between centre-side components and field devices may use a variety of
communication protocols, mostly depending on the physical link conditions, the vast majority of other
coloured links between centre-side components, internal to one organization or external to others, are
viii
based on an internet protocol (IP) network and mostly use the transmission control protocol (TCP)
transport layer protocol (user datagram protocol, UDP, is also possible in a few cases).
Nevertheless, as the different colours indicate, they can very well have significantly different
requirements. Internal links (blue) can reside in one domain of trust, hence do not require protocols
compatible with security gateways. This can already be different for links to other road operators
(red) and will certainly not hold for links to other types of organizations, like service providers, via the
Internet (green).
While different security requirements offer the most striking and obvious example, there are more
criteria that can lead to different preferences on different types of links, e.g. scalability, robustness and
integration complexity.
In broad terms, the colours blue – red – green form a hierarchy from more internal, closely-coupled,
well-integrated systems towards external, loosely-coupled and non-integrated systems. The world of
information and communication technology (ICT) offers a broad range of solutions for these different
scenarios, offering different advantages and disadvantages. It is clear that the one-size-fits-all principle
will not provide the most efficient way of working here. Even on the highest level of abstraction and
inside the ICT domain itself, a well-known battle of paradigms between remote-procedure-call (RPC)
type service specifications and RESTful architectures exists. The same clusters of options are found in
the domain of ITS standards, where for example the European standard for the real-time information
interface relating to public transport operations (SIRI; see the EN 15531 series) introduces both
concepts as complementary options: Publish-Subscribe and Request-Response.
Furthermore, the ITS station architecture is not in contradiction with this document but is
complementary to what is defined in this document. According to the principles and the taxonomy
defined in ISO 21217, this document defines a conceptual notion of:
— How two central ITS (sub-)stations could communicate to:
— deliver information (application data units);
— negotiate functional service behaviour for collaborating traffic management functions (even if
this use case could not directly be matched to ISO 21217 as it is not about information delivery).
— How a central ITS (sub-)station could communicate to deliver information (application data units)
to another ITS station with the characteristics of a central ITS station.
This document specifies the process of defining the exchange characteristics by use case-driven feature
selection of relevant parameters for the relevant OSI layers as defined in ISO 21217. Two exchange
schemas are considered: information delivery and functional service negotiation between central ITS
stations.
The drafting of this document was guided by the following principles:
— interoperability, such that different implementations can successfully engage in a data exchange
process;
— supporting of legacy implementations which are based on existing (exchange) specification, in order
to maximize investments already made by stakeholders;
— addressing other user profiles, not only road operators, thus making this document available to a
broader audience;
— reusing existing (communications) standards, in order to reduce implementation complexity and
take benefit of proven and already existing solutions for common ICT problems;
— maintaining a clear separation between the payload content and the exchange model.
Annex A details the adopted methodology for defining this exchange platform-independent model
(PIM).
ix
TECHNICAL SPECIFICATION ISO/TS 19468:2022(E)
Intelligent transport systems — Data interfaces between
centres for transport information and control systems
— Platform-independent model specifications for data
exchange protocols for transport information and control
systems
1 Scope
This document defines and specifies component facets supporting the exchange and shared usage of
data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the data content, structure and
relationships necessary and the communications specifications, in such a way that they are independent
from any defined technical platform.
This document establishes specifications for data exchange between any two instances of the following
actors:
— Traffic information centres (TICs);
— Traffic control centres/Traffic management centres (TCCs/TMCs);
— Service providers (SPs).
This document can also be applied for use by other actors, e.g. car park operators.
This document includes the following types of information:
— use cases and associated requirements, and features relative to different exchange situations;
— different functional exchange profiles;
— abstract elements for protocols;
— data model for exchange (informational structures, relationships, roles, attributes and associated
data types required).
In order to set up a new technical exchange framework, it is necessary to associate one functional
exchange profile with a technical platform providing an interoperability domain where plug-and-play
interoperability at a technical level can be expected. The definition of such interoperability domains
is out of scope of this document but can be found in other International Standards or Technical
Specifications (e.g. the ISO 14827 series).
This document is restricted to data exchange. Definition of payload content models is out of the scope
of this document.
2 Normative references
There are no normative references in this document.
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
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
business scenario
high-level description of the interactions that can exist within a system being analyzed or between the
system and external entities (called actors) in terms of business functions
Note 1 to entry: See also use case (3.21).
3.2
client
entity that receives the information
Note 1 to entry: It is represented in the information delivery business scenario (3.1).
3.3
exchange pattern
EP
basic exchange architecture template, described by UML communication diagrams, that identifies
the actors in the exchange framework and the available interactions among them, which enable data
exchange functionalities as a set of exchange features
Note 1 to entry: Exchange pattern interactions can be described by means of UML sequence diagrams and state
machine diagrams in such a way that message-triggering conditions are fully identified and defined alongside any
state update based on the subsequent interaction, i.e. exchanged messages and interaction-derived conditions.
3.4
collaborative ITS service
CIS
ITS service (3.7) that can be enabled by combing different “ITS services” that are provided by the
combined effort of two to more stakeholders who can have different roles
EXAMPLE Traffic management centres, traffic information centres, service providers.
3.5
functional exchange profile
FEP
selection of data exchange features for a particular business scenario (3.1)
3.6
interoperability domain
pair of functional exchange profile (FEP) (3.5) and platform selected for implementing a data exchange
subsystem
Note 1 to entry: Each platform-specific model (PSM) (3.11) document defines an interoperability domain, which
ensures that two implementations of this PSM are interoperable and can successfully exchange payload (3.9).
3.7
ITS service
processing of information to address specific ITS requirements and implement ITS features such as to
manage traffic or deliver information
3.8
payload content model
content model
UML definition of the data structures that can be used to describe travel and traffic information to be
exchanged in an exchange system
3.9
payload publication
payload
bundle of information that is exchanged between two exchange systems containing an instance of the
content model (3.8)
3.10
platform-independent model
PIM
document describing the abstract model of the standardized data exchange process in a platform-
independent way
Note 1 to entry: This definition is specific to this document.
3.11
platform-specific model
PSM
document providing the implementation details of a functional exchange profile (FEP) (3.5) described in
a platform-independent model (PIM) (3.10) for a concrete platform
Note 1 to entry: This definition is specific to this document.
3.12
profile-to-platform mapping
act of defining an interoperability domain (3.6)
3.13
pull exchange
exchange pattern (EP) (3.3) where the exchange of information is originated by the client (3.2)
3.14
push exchange
exchange pattern (EP) (3.3) where the exchange of information is originated by the supplier (3.20)
3.15
simple push
push-based exchange pattern (EP) (3.3) that does not require state to be maintained
3.16
snapshot
set of data providing all of the last known state as opposed to providing partial changes
Note 1 to entry: This definition is specific to this document.
3.17
snapshot pull
pull-based exchange pattern (EP) (3.3) where only the last snapshot (3.16) version is exchanged
3.18
snapshot push
push-based exchange pattern (EP) (3.3) where only the last snapshot (3.16) version is exchanged
3.19
stateful push
push-based exchange pattern (EP) (3.3) where data describing a communication session is maintained
across successive communication within that session
3.20
supplier
entity that provides the information
Note 1 to entry: It is represented in the information delivery business scenario (3.1).
3.21
use case
UC
set of operational interactions between entities (called actors) and a system to ease understanding of
the main functions behind such interactions
4 Symbols and abbreviated terms
ASN.1 Abstract Syntax Notation One
BUC business use case
F&L freight and logistic
HTTP hypertext transfer protocol
ICT information and communication technology
IP internet protocol
ITS intelligent transport systems
LOS level of service
MDA model-driven architecture
MMI man-machine interface
pub/sub publish-subscribe pattern
REST representational state transfer
RPC remote procedure call
SOAP simple object access protocol
SSL secure sockets layer
TCC traffic control centre
TMC traffic management centre
TIC traffic information centre
TIS traffic information service
TCP transmission control protocol
TLS transport layer security
TMP traffic management plan
UDDI universal description discovery and integration
UDP user datagram protocol
UML unified modeling language (see the ISO/IEC 19505 series)
VMS variable message sign
W3C world wide web consortium
WSDL web service definition language
WSIL web services inspection language
WSS web services security
XML extensible markup language
5 Exchange modeling framework
5.1 Overview
The model-driven approach is chosen to describe exchange: this leads to describing exchange systems
by means of abstract models, named platform-independent models (PIMs), in which the modeling of
exchange features is achieved by describing interactions among systems and subsystems as exchange
patterns (EPs). These interactions implement system capabilities as features that fulfil exchange
requirements requested by specific business scenarios which are used to describe specific uses of
exchange.
5.2 Business scenarios and functional exchange profiles
This document is based on business scenarios, i.e. a high-level description of the interactions that can
exist within a system being analyzed or between the system and external entities (called actors) in
terms of business functions. Business scenarios are derived from application requirements on useful
business information required and on technical capabilities enabled by available technologies. FEPs are
identified to ensure interoperable services with the restriction of determining one FEP per business
scenario for a specific EP, which is an abstract model of available technical platforms.
One business scenario can be supported by more than one FEP. FEPs can be enabled by several EPs
(Figure 2).
...