ISO 14827-3:2019

Transport information and control systems - Data interfaces between centres for transport information and control systems - Part 3: Data interfaces between centres for intelligent transport sytems (ITS) using XML (Profile A)

This document is applicable to data exchange between different systems. This document defines the message rules and procedures for communication between transport information and control systems using XML. This document clarifies how to package end-application messages and relevant data. This document defines the mechanism to request end-application data from the client and to deliver the requested data from the supplier. Several profiles are defined, however only Profile A is defined in this document. Other profiles will be defined in future parts of the ISO 14827 series of standards. A system can be both a client and a supplier of another system simultaneously, using multiple sessions.

Systèmes de commande et d'information des transports — Interfaces de données entre les centres pour systèmes de commande et d'information des transports — Partie 3: Interfaces de données entre centres pour systèmes intelligents de transport (ITS) utilisant XML

General Information

• Status: Published
• Publication Date: 06-Jan-2019
• ICS: 03.220.01 - Transport in general
• 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: 9093 - International Standard confirmed
• Start Date: 17-Dec-2025
• Completion Date: 27-Dec-2025

Overview

ISO 14827-3:2019 - Transport information and control systems - Part 3: Data interfaces between centres for intelligent transport systems (ITS) using XML (Profile A) - defines a Platform Specific Model (PSM) for XML-based data exchange between ITS centres. The standard specifies message rules and procedures to package end-application messages, request and deliver data between suppliers and clients, and manage sessions where a system can act as both client and supplier. It targets centre-to-centre communication interfaces and prescribes how to use common transport protocols without re-defining lower-layer packet exchange.

Key Topics and Requirements

• Message paradigms: Defines two primary exchange methods - Push (subscription/publication/receipt) and Pull (with or without SOAP).
• SOAP usage: SOAP is mandatory for Push exchanges; optional for Pull.
• Profile A (XML tag profile): Profile A is defined in this part and assumes interoperability with NTCIP 2306. Only Profile A is specified here; additional profiles will be added in later ISO 14827 parts.
• Message structure rules: XML messages must include XML version/encoding, a SOAP envelope with header and body, and follow prescribed subscription, publication and receipt structures.
• Functional Exchange Profile (FEP): Annex A provides a FEP - a selection of exchange features to implement.
• Supporting normative annexes: Annex B (XML tag scripts), Annex C (protocol usage methods), Annex D (informative message structures).
• Conformance: No explicit tests are defined; conformance is achieved when exchanged data conform to the messaging rules in the document.
• Scope exclusions: Lower-layer packet rules and specific end-application data definitions are out of scope.

Applications and Who Uses It

ISO 14827-3:2019 is intended for:

• ITS system architects and integrators designing centre-to-centre interfaces
• Traffic management centres, control centres, and data publishers/consumers in public and private sectors
• Software developers implementing XML/SOAP message handlers and session management
• Vendors ensuring interoperability with NTCIP 2306-aware centres

Practical uses include real-time traffic data subscriptions, event-driven alerts, periodic data publication, and standardized client/supplier interactions across heterogeneous ITS networks.

Related Standards

• ISO 14827-1: fundamental message requirements (PIM)
• ISO 14827-2: ASN.1-based PSM (note: ASN.1 formats are not compatible with the XML formats in Part 3)
• NTCIP 2306: referenced for XML message encoding and transport; Profile A assumes interconnection compatibility

Keywords: ISO 14827-3:2019, transport information and control systems, ITS, XML data interfaces, Push/Pull messaging, SOAP, Profile A, NTCIP 2306, Functional Exchange Profile (FEP)

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 14827-3
First edition
2019-01
Transport information and control
systems — Data interfaces between
centres for transport information and
control systems —
Part 3:
Data interfaces between centres for
intelligent transport sytems (ITS)
using XML (Profile A)
Systèmes de commande et d'information des transports — Interfaces
de données entre les centres pour systèmes de commande et
d'information des transports —
Partie 3: Interfaces de données entre centres pour systèmes
intelligents de transport (ITS) utilisant XML
Reference number
©
ISO 2019
© ISO 2019
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]
Fax: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii © ISO 2019 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 3
3 Terms and definitions . 3
4 Symbols and abbreviated terms . 4
5 Conformance . 5
6 Messaging rules . 5
6.1 General . 5
6.2 Push . 5
6.2.1 General. 5
6.2.2 General message structure . 6
6.2.3 Subscription message structure . 7
6.2.4 Publication message structure . 7
6.2.5 Receipt message structure . 8
6.3 Pull with SOAP . 8
6.3.1 General. 8
6.3.2 General message structure . 8
6.3.3 Request message structure . 9
6.3.4 Response message structure . 9
6.4 Pull without SOAP . 9
6.4.1 General. 9
6.4.2 General message structure .10
6.4.3 Request message structure .10
6.4.4 Response message structure .10
Annex A (normative) Functional Exchange Profile (FEP) .11
Annex B (normative) Tag scripts for composing XML messages .14
Annex C (normative) Protocol usage methods .24
Annex D (informative) Message structures .26
Bibliography .27
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.
A list of all parts in the ISO 14827 series can be found on the ISO website.
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.
iv © ISO 2019 – All rights reserved

Introduction
The relationship between this document and other standards in the ISO 14827 series is as follows.
ISO 14827-1 defines fundamental requirements of messages exchanged among centres. ISO 14827-2
defines ASN.1 formats to implement messages over ASN.1 platform. This document conforms to the
fundamental requirements defined in ISO 14827-1 and defines requirements on XML messages to
implement messages using XML. There is no compatibility between ASN.1 messages defined by
ISO 14827-2 and XML messages defined by this document.
This document is not intended to conflict with existing standards on interfaces of data exchange among
ITS centres.
INTERNATIONAL STANDARD ISO 14827-3:2019(E)
Transport information and control systems — Data
interfaces between centres for transport information and
control systems —
Part 3:
Data interfaces between centres for intelligent transport
sytems (ITS) using XML (Profile A)
1 Scope
This document is applicable to data exchange between different systems. This document defines the
message rules and procedures for communication between transport information and control systems
using XML. This document clarifies how to package end-application messages and relevant data. This
document defines the mechanism to request end-application data from the client and to deliver the
requested data from the supplier. Several profiles are defined, however only Profile A is defined in this
document. Other profiles will be defined in future parts of the ISO 14827 series of standards. A system
can be both a client and a supplier of another system simultaneously, using multiple sessions.
Figure 1 — Relationship between related documents
Rules and procedures for exchanging data-packets in lower layers are out of scope of this document.
These functionalities can be implemented using generic protocols defined in the industrial standards.
However this document defines how to use these protocols.
Data definition used in specific end-applications is out of scope in this document.
A network following this document comprises multiple kinds of systems. Each system can be viewed as
an element including databases and interfaces, as shown in Figure 2:
Key
1 application interface
2 operator interface
3 communication interface
4 database interface
5 communications cloud
6 system that makes a “subscription” or a “publication”
7 database
Figure 2 — System interfaces
This document is applicable to “communication interface” only. It is specified to meet the requirements
of communication between ITS centres. However, it is designed in a generic fashion and thus can be
used for data exchanges in other parts of the ITS field as well.
The framework for communication between centres using XML and the area that is prescribed by this
document is shown in Figure 3. This document defines message rules and procedures for communication
utilizing XML. In addition, this document explains how to use these protocols.
2 © ISO 2019 – All rights reserved

Figure 3 — Framework for transmissions between centres using XML and the
standardization area
This document defines a Platform Specific Model (PSM) for exchange, which specifically uses XML. A
PSM is an actual implementation of a Platform Independent Model (PIM) for exchange. A PIM is defined
in another standard. When implementing a specific PSM, a Functional Exchange Profile (FEP), which is
a selection of data exchange features, is identified. This document provides a FEP in Annex A.
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.
NTCIP 2306, National Transportation Communications for ITS Protocol, Application Profile for XML
Message Encoding and Transport in ITS Center-to-Center Communications, v01.69r, December 2008
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 http: //www .electropedia .org/
3.1
centre
computer or network that meets the requirements of a standardized communications interface over a
fixed-point communications network, regardless of whether the centre is the only system within the
building or just one of many, or even if the centre is in a remote location
Note 1 to entry: “Centres” include both government and private sector publishers and users of data.
3.2
client
computer or application that requests and accepts data from a supplier computer or application using a
protocol
3.3
message
data structure that is associated with a specific meaning and, when properly sent, an instance which
can convey information between systems
Note 1 to entry: For example, a data structure might include a list of speeds from detector stations. This single
data structure could be used to specify the content of several messages (e.g. the list of speeds currently being
detected, the list of stored speeds that will trigger a congestion warning if current values fall below the indicated
level, or a request for a list of locations where the current speed is less than the indicated speed). An instance of
the message would then contain the actual values.
3.4
publication
data which has been prepared by a supplier, and made available
3.5
receipt
data which is prepared by the receiver of the subscription or publication in order to acknowledge the order
3.6
subscription
data which is prepared by a client in order to request current or future publication(s)
3.7
supplier
computer or application that receives and responds to requests for data from client computers or
applications using a protocol
4 Symbols and abbreviated terms
FEP Functional Exchange Profile
GNU GNU is Not UNIX
GZIP GNU Zip
HTTP Hyper Text Transfer Protocol
ITS Intelligent Transport Systems
PIM Platform Independent Model
PSM Platform Specific Model
SOAP Simple Object Access Protocol
UCS Universal Multi-octet Coded Character Set
UTF UCS Transformation Format
XML Extensible Markup Language
4 © ISO 2019 – All rights reserved

5 Conformance
There are no explicit conformance tests in this document. Conformance is achieved if the exchange data
conform to the messaging rules of this document.
6 Messaging rules
6.1 General
This document provides requirements for creating XML messages exchanged between centres. These
XML messages do not apply to a specific application, but can be used by various applications. This
document deals with two methods for exchanging XML messages: “Push” and “Pull”.
Using SOAP is mandatory when exchanging information with Push. The formats of XML messages
for exchanging information by Push are described in 6.2. Using SOAP is optional when exchanging
information with Pull. The formats of XML messages for exchanging information by Pull with SOAP are
described in 6.3. The formats of XML messages for exchanging information by Pull without SOAP are
described in 6.4.
In creating XML messages, one XML tag profile shall be selected. Profile A supposes interconnection to
a centre conforming to NTCIP 2306. Details of Profile A are described in normative Annex B.
XML messages described in this clause are supposed to be transmitted over generic protocols for
communication (see normative Annex C).
6.2 Push
6.2.1 General
This subclause describes XML messages for exchanging information by Push. When centres exchange
information, a client subscribes for a supplier beforehand, and the supplier publishes messages to the
client periodically or on occurrence according to the subscription. A sequence diagram of subscription
is shown in Figure 4, a sequence diagram of publication on occurrence is shown in Figure 5, and a
sequence diagram of periodic publication is shown in Figure 6.
Subclause 6.2.2 describes common requirements for XML messages used for subscription, publication,
and receipt. Following that, 6.2.3 describes specific requirements for subscription messages, 6.2.4 for
publication messages, and 6.2.5 for receipt messages as well.
Figure 4 — Sequence diagram of Push subscription
Figure 5 — Sequence diagram of Push publication on occurrence
Figure 6 — Sequence diagram of Push periodic publication
6.2.2 General message structure
6.2.2.1 Introduction
This subclause describes common requirements for XML messages used for subscription, publication,
and receipt.
6.2.2.2 XML version and character encoding scheme
An XML message shall begin with a header specifying XML version and character encoding scheme.
6 © ISO 2019 – All rights reserved

6.2.2.3 SOAP envelope
An XML message shall contain a SOAP envelope.
6.2.2.4 SOAP header
A SOAP envelope shall contain a SOAP header.
6.2.2.5 SOAP body
A SOAP envelope shall contain a SOAP body.
6.2.3 Subscription message structure
6.2.3.1 Introduction
This subclause describes structures of XML messages used when clients subscribe for suppliers.
6.2.3.2 Profile A
A SOAP body shall contain a subscription header. The subscription header shall contain following:
— reference information (optional);
— subscription ID (mandatory);
— subscription name (optional);
— client address (mandatory);
— subscription type (mandatory);
— subscription operating code (mandatory);
— broadcast alert (optional);
— subscription time frame (optional);
— subscription frequency (optional).
The subscription time frame further contains two data elements: subscription start time and
subscription stop time.
6.2.4 Publication message structure
6.2.4.1 Introduction
This subclause describes structures of XML messages used when suppliers make publication to clients
after subscription.
6.2.4.2 Profile A
A SOAP body shall contain a publication header and a publication payload. The publication header shall
contain following:
— reference information (optional);
— subscription ID (mandatory);
— subscription name (optional);
— subscription count (mandatory).
6.2.5 Receipt message structure
6.2.5.1 Introduction
This subclause describes structures of XML messages used in receipts for subscriptions and
publications.
6.2.5.2 Profile A
A SOAP body shall contain a receipt header. The receipt header shall contain following:
— reference information (optional).
6.3 Pull with SOAP
6.3.1 General
This subclause describes XML messages for exchanging information by Pull with SOAP. When centres
exchange information, a client makes a request for a supplier, and the supplier makes a response to the
client. A sequence diagram of Pull with SOAP is shown in Figure 7. Subclause 6.3.2 describes common
requirements for XML messages used for request and response. Following that, 6.3.3 describes specific
requirements for request messages and 6.3.4 for response messages as well.
Figure 7 — Sequence diagram of Pull with SOAP
6.3.2 General message structure
6.3.2.1 Introduction
This subclause describes common requirements for XML messages used for request and response.
6.3.2.2 XML version and character encoding scheme
An XML message shall begin with a header specifying XML version and character encoding scheme.
6.3.2.3 SOAP envelope
An XML message shall contain a SOAP envelope.
8 © ISO 2019 – All rights reserved

6.3.2.4 SOAP header
A SOAP envelope shall contain a SOAP header.
6.3.2.5 SOAP body
A SOAP envelope shall contain a SOAP body.
6.3.3 Request message structure
6.3.3.1 Introduction
This subclause describes structures of XML messages used when clients make a request for suppliers.
6.3.3.2 Profile A
A SOAP body shall contain a request payload.
6.3.4 Response message structure
6.3.4.1 Introduction
This subclause describes structures of XML messages used when suppliers make response to clients.
6.3.4.2 Profile A
A SOAP body shall contain a response payload.
6.4 Pull without SOAP
6.4.1 General
This subclause describes XML messages for exchanging information by Pull without SOAP. When centres
exchange information, a client makes a request for a
...