ISO/TS 14827-4:2022
(Main)Intelligent transport systems — Data interfaces between centres for transport information and control systems — Part 4: Data interfaces between centres for Intelligent transport systems (ITS) using XML (Profile B)
Intelligent transport systems — Data interfaces between centres for transport information and control systems — Part 4: Data interfaces between centres for Intelligent transport systems (ITS) using XML (Profile B)
This document, based on ISO/TS 19468, specifies a platform-specific method for implementing data exchange among centres based on simple object access protocol (SOAP), supporting the EN 16157 series (DATEX II) for Push/Pull data delivery and service request/feedback collaborative intelligent transport system (ITS) services. This document defines the message rules and procedures for communication between transport information and control systems using XML (Profile B). This document clarifies how to package end-application messages and relevant data. The payload data definition used in specific end-applications and the exact structure of the content payload delivered in the messages are beyond the scope of this document. Rules and procedures for exchanging data-packets in lower communication layers are also out of the scope of this document. These functionalities can be implemented using generic protocols defined in the industry standards. However, this document does define how to use these protocols.
Systèmes de transport intelligents - Interface de données entre centres pour les systèmes de commande et d'information des transports — Partie 4: Interfaces de données entre centres pour systèmes de transport intelligents (ITS) utilisant XML (Profil B)
General Information
Relations
Buy Standard
Standards Content (Sample)
TECHNICAL ISO/TS
SPECIFICATION 14827-4
First edition
2022-09
Intelligent transport systems —
Data interfaces between centres for
transport information and control
systems —
Part 4:
Data interfaces between centres for
Intelligent transport systems (ITS)
using XML (Profile B)
Systèmes de transport intelligents - Interface de données entre centres
pour les systèmes de commande et d'information des transports —
Partie 4: Interfaces de données entre centres pour systèmes de
transport intelligents (ITS) utilisant XML (Profil B)
Reference number
ISO/TS 14827-4:2022(E)
© ISO 2022
---------------------- Page: 1 ----------------------
ISO/TS 14827-4:2022(E)
COPYRIGHT PROTECTED DOCUMENT
© 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: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
© ISO 2022 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/TS 14827-4:2022(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 1
5 Conformance . 2
6 Exchange modelling framework .2
6.1 Web services definition and options . 3
6.2 Web services PSM mapping of FEP+EP PIMs . 3
6.3 Security aspects related to WS implementation . 4
7 Data Delivery FEP+EP PSM definition . 4
7.1 Overview of Data Delivery PSM definition . 4
7.2 Profile B Snapshot Pull SOAP WS PSM definition . 4
7.3 Profile B Snapshot Push SOAP WS PSM definition . 5
7.4 Profile B Simple Push SOAP WS PSM definition . 5
7.5 Profile B Stateful Push SOAP WS PSM definition . 5
8 Collaborative ITS Services FEP+EP PSM definition . 6
8.1 Overview of Collaborative ITS Service (CIS) PSM definition . 6
8.2 Profile B Simple CIS SOAP WS PSM definition . 6
8.3 Stateful CIS . 6
Annex A (informative) Schemas and WSDL definitions . 8
Annex B (informative) "Snapshot Pull with simple http server” profile definition .10
Bibliography .17
iii
© ISO 2022 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/TS 14827-4:2022(E)
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).
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 2022 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/TS 14827-4:2022(E)
Introduction
Data exchange among centres is a baseline service for implementing intelligent transport system
(ITS) services. For interoperability purposes, data delivery and collaborative ITS services need to be
implemented according to certain specifications based on fully-described interfaces. The functional
exchange profiles implementing push and pull exchange patterns aim to guarantee timely and reliable
delivery of information, based on a defined level of service and user requirements. These depend on
application level. A variety of options for implementing exchange are therefore described. These enable
several interoperable exchange patterns with required features to fully satisfy user requirements:
from Snapshot Pull/Push to Simple Push to Stateful Push, also considering a service request/service
feedback collaborative ITS services business scenario, which allows interoperable exchange among
any number of interconnected and collaborating elements to implement traffic management and traffic
information services orchestrated among several ITS actors.
This document aims to define and describe the requirements on XML messages for implementing
messages using XML Profile B. In particular, it is intended to be used in platform-specific implementations
using simple object access protocol (SOAP) web services to enable DATEX II (EN 16157-1) XML coded
messages for Snapshot Pull, Snapshot Push, Simple Push and Stateful Push. It is additionally relevant
to collaborative ITS services (CISs) such as Simple CIS and Stateful CIS exchange patterns with relative
functional exchange profiles as described by ISO/TS 19468. Figure 1 describes the relationship between
exchange-related documents.
Key
PIM platform-independent model
EP exchange pattern
FEP functional exchange profile
PSM platform-specific model
Figure 1 — Relationship between exchange-related documents
The message structure defined in this document refers to the "basic exchange data model" and derived
data dictionary defined in ISO/TS 19468:2022, Annex C, which is implemented in XML schema by the
DATEX II methodology defined in EN 16157-1.
This document is not intended to conflict with existing standards on interfaces of data exchange among
ITS centres.
v
© ISO 2022 – All rights reserved
---------------------- Page: 5 ----------------------
TECHNICAL SPECIFICATION ISO/TS 14827-4:2022(E)
Intelligent transport systems — Data interfaces between
centres for transport information and control systems —
Part 4:
Data interfaces between centres for Intelligent transport
systems (ITS) using XML (Profile B)
1 Scope
This document, based on ISO/TS 19468, specifies a platform-specific method for implementing data
exchange among centres based on simple object access protocol (SOAP), supporting the EN 16157 series
(DATEX II) for Push/Pull data delivery and service request/feedback collaborative intelligent transport
system (ITS) services.
This document defines the message rules and procedures for communication between transport
information and control systems using XML (Profile B).
This document clarifies how to package end-application messages and relevant data.
The payload data definition used in specific end-applications and the exact structure of the content
payload delivered in the messages are beyond the scope of this document.
Rules and procedures for exchanging data-packets in lower communication layers are also out of the
scope of this document. These functionalities can be implemented using generic protocols defined in
the industry standards. However, this document does define how to use these protocols.
2 Normative references
The following documents are referred to in the text in such a way that some of or all their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/TS 19468, 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
RFC 2616, Hypertext Transfer Protocol — HTTP/1.1
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/TS 19468 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/
4 Abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO/TS 19468 and the following
apply
1
© ISO 2022 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/TS 14827-4:2022(E)
B2B business to business
CIS collaborative ITS services
EP exchange pattern
FEP functional exchange profile
IANA Internet Assigned Numbers Authority
ITS intelligent transport systems
PIM platform-independent model
PSM platform-specific model
SAML security assertions markup language
UCS universal multi-octet coded character set
UTF UCS transfer format
VMS variable message sign
WS web service
XACML extensible access control markup language
XMLDSG XML digital signature
XMLENC XML encryption
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 Exchange modelling framework
The model-driven approach defined in ISO/TS 19468 is resumed in Figure 2.
2
© ISO 2022 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/TS 14827-4:2022(E)
Key
PIM platform-independent model
EP exchange pattern
FEP functional exchange profile
PSM platform-specific model
VMS variable message sign
Figure 2 — Model-driven approach from ISO/TS 19468
This document describes the mapping rules in order to implement specific platform Push and Pull
and collaborative ITS services (CIS) FEP+EP-based PIM in SOAP web services technology PSMs. PIM-
level descriptions of FEP+EP are detailed in ISO/TS 19468; the relevant clauses are referenced in this
document.
6.1 Web services definition and options
Web services (WSs) provide standard means of interoperating between different software applications,
running on a variety of platforms and/or frameworks. A full definition for "web service" can be found
in Reference [6].
Web service definitions offer several options. Table 1 shows the options chosen by the PSMs described
in this document.
Table 1 — Web service options
Web service options Decision
Discovery Not dynamic: universal description discovery and integration(UD-
DI) is not used; the WSs are described at https:// standards .iso .org/
iso/ ts/ 14827/ -4/ ed -1/ en.
Security The security set-up shall be decided by the supplier, should be ne-
gotiated with the clients, and is outside the scope of this document.
Encryption This shall be agreed between the supplier and the client before
starting the data exchange.
6.2 Web services PSM mapping of FEP+EP PIMs
PIM specification to implement FEP+EP PIM based on WS SOAP technology consists in mapping the
abstract unified modeling language (UML) messages (invocation methods and data types) defined
3
© ISO 2022 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/TS 14827-4:2022(E)
at FEP+EP PIM level as UML collaboration and sequence diagrams in ISO/TS 19468 clauses to the
corresponding SOAP web service definition language (WSDL) methods and data structure.
6.3 Security aspects related to WS implementation
As described in ISO/TS 19468, security aspects are considered in the exchange specification framework
in the general context diagrams, under the aspects of communication features. Security features are
described in ISO/TS 19468:2022, 5.7, while security requirements are defined in ISO/TS 19468:2022,
Annex B.
As this document is based on exchange communication among centres based on XML, Profile B (e.g.
under SOAP webservices and supporting DATEX II), security for such exchange framework based on WS
may rely on the WS-security OASIS international standard specification which is widely used within
several frameworks (e.g. the JAVA wsse4j, jax-ws, or the .NET WCF). Some aspects of WS-security are
also introduced in ISO/TS 19468:2022, Annex D.
The WS-security framework is composed by profiles that define the interoperability rules to be
used to attain specific features. Those profiles tackle the necessity to exchange an identification and
authentication token (e.g. the username token profile), or how to use XML digital signature (XMLDSG)
and XML encryption (XMLENC) to sign and encrypt parts of a SOAP message, respectively, or to support
complex scenarios through the combined use of security assertions markup language (SAML) tokens
and potentially extensible access control markup language (XACML) access control policies.
WS-Security needs further profiling before its use which is, usually, policy specific (e.g. which algorithm
and cipher-suites to be used, canonicalization algorithms, token layouts, compliance with WS-BSP, etc.).
This profiling effort which can be specifically based on regional or project specific rules, is outside the
scope of the current specification.
7 Data Delivery FEP+EP PSM definition
7.1 Overview of Data Delivery PSM definition
The following clauses express requirements for implementation of data delivery business scenarios
FEP+EP which are fully described at PIM level in ISO/TS 19468 by referencing their exchange agent and
relative interfaces.
NOTE A system can be both a client and a supplier of another system simultaneously, defining multiple
separated exchange contexts (e.g. set of exchange nodes defined to exchange information in a specific business
scenario with a specified EP+FEP).
7.2 Profile B Snapshot Pull SOAP WS PSM definition
The Profile B Snapshot Pull SOAP WS implementation is defined according to the Snapshot Pull FEP +
EP PIM description which is described in ISO/TS 19468:2022, Clause 6, where "Snapshot Pull" exchange
system functional characteristics and features implementation are fully described.
In the Profile B Snapshot Pull SOAP WS exchange interface, the SOAP WSDL supplier method to
implement pullSnapshotData shall be the WSDL method named "pullSnapshotData" which shall not
require any input and shall return a "MessageContainer" information XML message data structure.
Messages are implemented by SOAP protocol adding SOAP envelope information. The corresponding
WSDL file is given in Annex A of the present document. The XSD definition for Message Container is also
described in Annex A.
4
© ISO 2022 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/TS 14827-4:2022(E)
7.3 Profile B Snapshot Push SOAP WS PSM definition
The Profile B Snapshot Push SOAP WS implementation is defined according to the Snapshot Push FEP +
EP PIM description which is described in ISO/TS 19468:2022, Clause 7, where Snapshot Push exchange
system functional characteristics and features are fully described.
In the Profile B Snapshot Push SOAP WS exchange interface, the SOAP WSDL client method to implement
putSnapshotData shall be the WSDL method named "putSnapshotData" which shall accept as input
a "MessageContainer" XML message data structure and shall return an "ExchangeInformation" XML
message data structure.
Messages are implemented by SOAP protocol adding SOAP envelope information. The corresponding
WSDL file is given in Annex A of the present document. XSD definitions for Message Container and
Exchange Information are also described in Annex A.
7.4 Profile B Simple Push SOAP WS PSM definition
The Profile B Simple Push SOAP WS implementation is defined according to the Simple Push FEP + EP
PIM description which is described in ISO/TS 19468:2022, Clause 8, where "Simple Push" exchange
system functional characteristics and features are fully described.
In the Profile B Simple Push SOAP WS exchange interface:
— the SOAP WSDL client method to implement putSnapshotData shall be the WSDL method named
"putSnapshotData" which shall accept as input a "MessageContainer" XML message data structure
and shall return an "ExchangeInformation" XML message data structure;
— the SOAP WSDL client method to implement putData shall be the WSDL method named "putData"
which shall accept as input a "MessageContainer" XML message data structure and shall return an
"ExchangeInformation" XML message data structure;
— the SOAP WSDL client method to implement keepAlive shall be the WSDL method named "keepAlive"
which shall accept as input an "ExchangeInformation" XML message data structure and shall return
an "ExchangeInformation" XML message data structure;
Messages are implemented by SOAP protocol adding SOAP envelope information. The corresponding
WSDL file is given in Annex A of the present document. XSD definitions for Message Container and
Exchange Information are also described in Annex A.
7.5 Profile B Stateful Push SOAP WS PSM definition
The Profile B Stateful Push SOAP WS implementation is defined according to the Stateful Push FEP +
EP PIM description which is described in ISO/TS 19468:2022, Clause 9, where Stateful Push exchange
system functional characteristics and features are fully described.
In the Profile B Stateful Push SOAP WS exchange interface:
— the SOAP WSDL client method to implement openSession shall be the WSDL method named
"openSession" which shall accept as input an "ExchangeInformation" XML message data structure
and shall return an "ExchangeInformation" XML message data structure;
— the SOAP WSDL client method to implement closeSession shall be the WSDL method named
"closeSession" which shall accept as input an "ExchangeInformation" XML message data structure
and shall return an "ExchangeInformation" XML message data structure;
— the SOAP WSDL client method to implement putSnapshotData shall be the WSDL method named
"putSnapshotData" which shall accept as input a "MessageContainer" XML message data structure
and shall return an "ExchangeInformation" XML message data structure;
5
© ISO 2022 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/TS 14827-4:2022(E)
— the SOAP WSDL client method to implement putData shall be the WSDL method named "putData"
which shall accept as input a "MessageContainer" XML message data structure and shall return an
"ExchangeInformation" XML message data structure;
— the SOAP WSDL client method to implement keepAlive shall be the WSDL method named "keepAlive"
which shall accept as input an "ExchangeInformation" XML message data structure and shall return
an "ExchangeInformation" XML message data structure.
Messages are implemented by SOAP protocol adding SOAP envelope information. The corresponding
WSDL file is given in Annex A of the present document. XSD definitions for Message Container and
Exchange Information are fully described in Annex A.
8 Collaborative ITS Services FEP+EP PSM definition
8.1 Overview of Collaborative ITS Service (CIS) PSM definition
The following subclauses express requirements for the implementation of collaborative ITS service
(CIS) business scenario FEP+EPs (which are fully described at PIM level in ISO/TS 19468) by referencing
their exchange agent and relative interfaces.
NOTE A system can be simultaneously both a CIS requester and a CIS provider for another CIS requester,
defining multiple separated CIS exchange contexts (e.g. set of exchange nodes defined to exchange information in
a specific business scenario with a specified EP+FEP).
8.2 Profile B Simple CIS SOAP WS PSM definition
The Profile B Simple CIS SOAP WS implementation is defined according to the Simple CIS FEP + EP PIM
description which is described in ISO/TS 19468:2022, Clause 10, where the exchange system functional
characteristics and features are fully described.
In the Profile B Simple CIS SOAP WS exchange interface at the service provider side:
— the SOAP WSDL method to implement putCISServiceRequest shall be the WSDL method named
"putCISServiceRequest" which shall accept as input a "MessageContainer" XML message data
structure and shall return an "ExchangeInformation" XML message data structure.
In the Profile B Simple CIS SOAP WS exchange interface at the service requester side:
— the SOAP WSDL method to implement putCISServiceFeedback shall be the WSDL method named
"putCISServiceRequest" which shall accept as input a "MessageContainer" XML message data
structure and shall return an "ExchangeInformation" XML message data structure.
Messages are implemented by SOAP adding SOAP envelope information.
The corresponding WSDL file is given in Annex A of the present document. XSD definitions for Message
Container and Exchange Information are also described in Annex A.
8.3 Stateful CIS
The Profile B Stateful CIS SOAP WS implementation is defined according to the Stateful CIS FEP + EP
PIM description which is described in ISO/TS 19468:2022, Clause 11, where this exchange system
functional characteristics and features are fully described.
In the Profile B Simple CIS SOAP WS exchange interface at the service provider side:
— the SOAP WSDL method to implement putCISServiceRequest shall be the WSDL method named
"putCISServiceRequest" which shall accept as input a "MessageContainer" XML message data
structure and shall return an "ExchangeInformation" XML message data structure;
6
© ISO 2022 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/TS 14827-4:2022(E)
— the SOAP WSDL client method to implement openSession shall be the WSDL method named
"openSession" which shall accept as input an "ExchangeInformation" XML message data structure
and shall return an "ExchangeInformation" XML message data structure;
— the SOAP WSDL client method to implement closeSession shall be the WSDL method named
"closeSession" which shall accept as input an "ExchangeInformation" XML message data structure
and shall return an "ExchangeInformation" XML message data structure;
— the SOAP WSDL client method to implement keepAlive shall be the WSDL method named "keepAlive"
which shall accept as input an "ExchangeInformation" XML message data structure and shall return
an "ExchangeInformation" XML message data structure.
In the Profile B Simple CIS SOAP WS exchange interface at the service requester side:
— the SOAP WSDL method to implement putCISServiceFeedback shall be the WSDL method named
"putCISServiceRequest" which shall accept as input an "MessageContainer" XML message data
structure and shall return an "ExchangeInformation" XML message data structure.
Messages are implemented by SOAP adding SOAP envelope information. The corresponding WSDL
file is given in Annex A of the present document. XSD definitions for Message Container and Exchange
Information are also described in Annex A.
7
© ISO 2022 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/TS 14827-4:2022(E)
Annex A
(informative)
Schemas and WSDL definitions
A.1 WSDL definitions
A.1.1 Profile B Snapshot Pull SOAP WSDL definition
The machine-readable file for this definition can be found at https:// standards .iso .org/ iso/ ts/ 14827/
-4/ ed -1/ en.
A.1.2 Profile B Snapshot Push SOAP WSDL definition
The machine-readable file for this definition can be found at https:// standards .iso .org/ iso/ ts/ 14827/
-4/ ed -1/ en.
A.1.3 Profile B Simple Push SOAP WSDL definition
The machine-readable file for this definition can be found at https:// standards .iso .org/ iso/ ts/ 14827/
-4/ ed -1/ en.
A.1.4 Profile B Stateful Push SOAP WSDL definition
The machine-readable file for this definition can be found at https:// standards .iso .org/ iso/ ts/ 14827/
-4/ ed -1/ en.
A.1.5 Profile B Simple CIS SOAP WSDL definition
The machine-readable file for this definition can be found at https:// standards .iso .org/ iso/ ts/ 14827/
-4/ ed -1/ en.
A.1.6 Stateful CIS WSDL definition
The machine-readable file for this definition can be found at https:// standards .iso .org/ iso/ ts/ 14827/
-4/ ed -1/ en.
A.1.7 Full Exchange WSDL definition
The machine-readable file for the extended union of all FEP+EP implementation described in this
document can be found at https:// standards .iso .org/ iso/ ts/ 14827/ -4/ ed -1/ en.
A.2 XML schemas for exchange-related content
A.2.1 Message Container
The machine-readable file for Message Container can be found at https:// standards .iso .org/ iso/ ts/
14827/ -4/ ed -1/ en.
A.2.2 Exchange Information XML schema definition
The machine-readable file for this definition can be found at https:// standards .iso .org/ iso/ ts/ 14827/
-4/ ed -1/ en.
8
© ISO 2022 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/TS 14827-4:2022(E)
A.2.3 Information Management XML schema definition
The machine-readable file for this definition can be found at https:// standards .iso .org/ iso/ ts/ 14827/
-4/ ed -1/ en.
A.2.4 CIS Information XML schema definition
The machine-readable file for this definition can be found at https:// standards .iso .org/ iso/ ts/ 14827/
-4/ ed -1/ en.
A.3 Snapshot Pull with simple http server profile definition
The machine-readable file f
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.