ISO/TS 21219-18:2015
(Main)Intelligent transport systems - Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) — Part 18: Traffic flow and prediction application (TPEG2-TFP)
Intelligent transport systems - Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) — Part 18: Traffic flow and prediction application (TPEG2-TFP)
ISO/TS 21219-18:2015 specifies the TPEG application Traffic Flow and Prediction (TFP). It has been specifically designed to provide information to a variety of receivers using different channels, including in the first instance Digital Broadcasting and Internet technologies. Traffic flow and prediction messages are intended for in-car applications and may be as well presented directly to the user by textual, voiced and graphically output devices.
Systèmes intelligents de transport — Informations sur le trafic et le tourisme via le groupe expert du protocole de transport, génération 2 (TPEG2) — Partie 18: Flux de trafic et application de prédiction (TPEG2-TFP)
General Information
Relations
Standards Content (Sample)
TECHNICAL ISO/TS
SPECIFICATION 21219-18
First edition
2015-03-01
Intelligent transport systems - Traffic
and travel information (TTI) via
transport protocol experts group,
generation 2 (TPEG2) —
Part 18:
Traffic flow and prediction
application (TPEG2-TFP)
Systèmes intelligents de transport — Informations sur le trafic
et le tourisme via le groupe expert du protocole de transport,
génération 2 (TPEG2) —
Partie 18: Flux de trafic et application de prédiction (TPEG2-TFP)
Reference number
ISO/TS 21219-18:2015(E)
©
ISO 2015
---------------------- Page: 1 ----------------------
ISO/TS 21219-18:2015(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2015
All rights reserved. Unless otherwise specified, 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
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2015 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/TS 21219-18:2015(E)
Contents Page
Foreword .iv
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Abbreviated terms . 3
4 Application specific constraints . 3
5 TFP Structure . 5
6 TFP Message components . 5
6.1 TFPMessage . 5
6.2 MessageManagementContainer . 6
6.3 LocationReferencingContainer . 7
6.4 TFPMethod . 7
6.5 FlowPolygonObject . 8
6.6 FlowPolygon . 9
6.7 FlowStatus . 9
6.8 FlowMatrix .10
6.9 FlowVector .14
6.10 SectionExtensionComponent .15
6.11 RestrictionExtensionComponent .15
6.12 StatusExtensionComponent .15
6.13 StatisticsExtensionComponent .15
7 TFP Data Types .15
7.1 PolygonPoint .16
7.2 FlowVectorSection .16
7.3 StatusParameters .17
7.4 Restrictions .17
7.5 StatisticalParameters.18
7.6 LinkedCause .19
8 TFP Tables .19
8.1 tfp001: VehicleClass .19
8.2 tfp002: VehicleCredentials .20
8.3 tfp003: LevelOfService .20
8.4 tfp004: SpatialResolution .22
8.5 tfp005:laneRestriction .22
8.6 tfp006: CauseCode .23
8.7 tfp007: SectionType.26
8.8 tfp008: FlowDataQuality .27
Annex A (normative) Traffic Flow and Prediction, TPEG-Binary Representation .28
Annex B (normative) Traffic Flow and Prediction, TPEG-ML Representation .38
Bibliography .49
© ISO 2015 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/TS 21219-18:2015(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 and TISA 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 on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical Barriers
to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/TC 204 Intelligent transport systems, in cooperation
with the Traveller Information Services Association (TISA), TPEG Applications Working Group through
Category A Liaison status.
ISO/TS 21219 consists of the following parts, under the general title Intelligent transport systems —
Traffic and travel information (TTI) via transport protocol expert group, generation 2 (TPEG2):
— Part 2: UML modelling rules [Technical Specification]
— Part 3: UML to binary conversion rules [Technical Specification]
— Part 4: UML to XML conversion rules [Technical Specification]
— Part 5: Service framework [Technical Specification]
— Part 6: Message management container [Technical Specification]
— Part 7: Location referencing container [Technical Specification]
— Part 18: Traffic flow and prediction application [Technical Specification]
The following parts are planned:
— Part 1: Introduction, numbering and versions [Technical Specification]
— Part 9: Service and network information [Technical Specification]
— Part 10: Conditional access information [Technical Specification]
— Part 14: Parking information application [Technical Specification]
— Part 15: Traffic event compact application [Technical Specification]
— Part 16: Fuel price information application [Technical Specification]
iv © ISO 2015 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/TS 21219-18:2015(E)
— Part 19: Weather information application [Technical Specification]
— Part 20: Extended TMC location referencing [Technical Specification]
— Part 21: Geographic location referencing [Technical Specification]
— Part 22: OpenLR·location·referencing [Technical Specification]
— Part 23: Roads·and·multi-modal·routes·application [Technical Specification]
© ISO 2015 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/TS 21219-18:2015(E)
Introduction
History
TPEG technology was originally proposed by the European Broadcasting Union (EBU) Broadcast
Management Committee, who established the B/TPEG project group in the autumn of 1997 with a brief
to develop, as soon as possible, a new protocol for broadcasting traffic and travel-related information
in the multimedia environment. TPEG technology, its applications and service features were designed
to enable travel-related messages to be coded, decoded, filtered and understood by humans (visually
and/or audibly in the user’s language) and by agent systems. Originally a byte-oriented data stream
format, which may be carried on almost any digital bearer with an appropriate adaptation layer, was
developed. Hierarchically structured TPEG messages from service providers to end-users were designed
to transfer information from the service provider database to an end-user’s equipment.
One year later in December 1998, the B/TPEG group produced its first EBU specifications. Two documents
were released. Part 2 (TPEG-SSF, which became ISO/TS 18234-2) described the Syntax, Semantics and
Framing structure, which was used for all TPEG applications. Meanwhile Part 4 (TPEG-RTM, which
became ISO/TS 18234-4) described the first application, for Road Traffic Messages.
Subsequently in March 1999, CEN TC 278/WG 4, in conjunction with ISO/TC 204/WG 10, established a
project group comprising members of the former EBU B/TPEG and they continued the work concurrently.
Further parts were developed to make the initial set of four parts, enabling the implementation of a
consistent service. Part 3 (TPEG-SNI, ISO/TS 18234-3) described the Service and Network Information
Application, used by all service implementations to ensure appropriate referencing from one service
source to another.
Part 1 (TPEG-INV, ISO/TS 18234-1), completed the series, by describing the other parts and their
relationship; it also contained the application IDs used within the other parts. Additionally, Part 5,
the Public Transport Information Application (TPEG-PTI, ISO/TS 18234-5), was developed. The so-
called TPEG-LOC location referencing method, which enabled both map-based TPEG-decoders and non
map-based ones to deliver either map-based location referencing or human readable text information,
was issued as ISO/TS 18234-6 to be used in association with the other applications parts of the
ISO/TS 18234-series to provide location referencing.
The ISO/TS 18234-series has become known as TPEG Generation 1.
TPEG Generation 2
With the inauguration of the Traveller Information Services Association (TISA) in December 2007
derived from former Forums and the CEN/ISO development project group, the TPEG Applications
Working Group took over development work for TPEG technology.
It was about this time that the (then) new Unified Modelling Language (UML) was seen as having major
advantages for the development of new TPEG Applications in communities who would not necessarily
have binary physical format skills required to extend the original TPEG TS work. It was also realized
that the XML format for TPEG described within the ISO/TS 24530-series (now superseded) had a greater
significance than previously foreseen; especially in the content-generation segment and that keeping
two physical formats in synchronism, in different standards series, would be rather difficult.
As a result TISA set about the development of a new TPEG structure that would be UML based – this has
subsequently become known as TPEG Generation 2.
TPEG2 is embodied in the ISO/TS 21219-series and it comprises many parts that cover introduction,
rules, toolkit and application components. TPEG2 is built around UML modelling and has a core of rules
that contain the modelling strategy covered in Parts 2, 3, 4 and the conversion to two current physical
formats: binary and XML; others could be added in the future. TISA uses an automated tool to convert
from the agreed UML model XMI file directly into an MS Word document file, to minimize drafting
errors, that forms the Annex for each physical format.
vi © ISO 2015 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/TS 21219-18:2015(E)
TPEG2 has a three container conceptual structure: Message Management (Part 6), Application (many
Parts) and Location Referencing (Part 7). This structure has flexible capability and can accommodate
many differing use cases that have been proposed within the TTI sector and wider for hierarchical
message content.
TPEG2 also has many location referencing options as required by the service provider community,
any of which may be delivered by vectoring data included in the Location Referencing Container. The
following classification provides a helpful grouping of the different TPEG2 parts according to their
intended purpose:
Toolkit parts: TPEG2-INV (Part 1), TPEG2-UML (Part 2), TPEG2-UBCR (Part 3), TPEG2-UXCR (Part 4),
TPEG2-SFW (Part 5), TPEG2-MMC (Part 6), TPEG2-LRC (Part 7)
Special applications: TPEG2-SNI (Part 9), TPEG2-CAI (Part 10)
Location referencing: TPEG2-ULR (Part 11), TPEG2-ETL (Part 20), TPEG2-GLR (Part 21), TPEG2-OLR
(Part 22)
Applications: TPEG2-PKI (Part 14), TPEG2-TEC (Part 15), TPEG2-FPI (Part 16), TPEG2-TFP (Part 18),
TPEG2-WEA (Part 19), TPEG2-RMR (Part 23)
TPEG2 has been developed to be broadly (but not totally) backward compatible with TPEG1 to assist in
transitions from earlier implementations, while not hindering the TPEG2 innovative approach and being
able to support many new features, such as dealing with applications having both long-term, unchanging
content and highly dynamic content, such as Parking Information.
This Technical Specification is based on the TISA specification technical/editorial version number:
TPEG2-TFP/1.0/003.
© ISO 2015 – All rights reserved vii
---------------------- Page: 7 ----------------------
TECHNICAL SPECIFICATION ISO/TS 21219-18:2015(E)
Intelligent transport systems - Traffic and travel
information (TTI) via transport protocol experts group,
generation 2 (TPEG2) —
Part 18:
Traffic flow and prediction application (TPEG2-TFP)
1 Scope
This Technical Specification specifies the TPEG application Traffic Flow and Prediction (TFP). It has been
specifically designed to provide information to a variety of receivers using different channels, including
in the first instance Digital Broadcasting and Internet technologies. Traffic flow and prediction messages
are intended for in-car applications and may be as well presented directly to the user by textual, voiced
and graphically output devices.
TFP is status oriented, i.e. the transmitted information updates continuously the receiver’s knowledge
for a dedicated road network. In particular the traffic states are delivered any time and for all road
sections of the network, even when there are no abnormal traffic situations.
Generally, TFP focuses on the following requirements:
— provide dynamic navigation systems with up-to-date traffic state information,
— ensure travel safety for the driver,
— enable the calculation of alternative routes,
— avoid delays (e.g. traffic jams),
— lower traffic load on over-saturated parts of the network,
— keep driver informed about current and upcoming traffic,
— compact and efficient coding of the traffic information.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO 17572-1:2008, Intelligent transport systems (ITS) — Location referencing for geographic databases —
Part 1: General requirements and conceptual model
ISO 17572-2:2008, Intelligent transport systems (ITS) — Location referencing for geographic databases —
Part 2: Pre-coded location references (pre-coded profile)
ISO 17572-3:2008, Intelligent transport systems (ITS) — Location referencing for geographic databases —
Part 3: Dynamic location references (dynamic profile)
ISO/TS 18234-1:2013, Intelligent transport systems — Traffic and travel information via transport
protocol experts group, generation 1 (TPEG1) binary data format — Part 1: Introduction, numbering and
versions (TPEG1-INV)
© ISO 2015 – All rights reserved 1
---------------------- Page: 8 ----------------------
ISO/TS 21219-18:2015(E)
ISO/TS 18234-6:2006, Traffic and Travel Information (TTI) — TTI via Transport Protocol Expert Group
(TPEG) data-streams — Part 6: Location referencing applications
ISO/TS 21219-2, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2) — Part 2: UML modelling rules
ISO/TS 21219-3, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2) — Part 3: UML to binary conversion rules
ISO/TS 21219-4, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2) — Part 4: UML to XML conversion rules
ISO/TS 21219-5, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2 — Part 5: Service framework (TPEG2-SWF)
ISO/TS 21219-6, Intelligent transport systems — Traffic and travel information via transport protocol
experts group, generation 2(TPEG2) — Part 6: Message management container (TPEG2-MMC)
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1.1
Message Management Container
concept applied to the grouping of all message elements including Message Management Information of
a TPEG-Message together in one place
3.1.2
Location Referencing
means to provide information that allows a system to accurately identify a location
Note 1 to entry: The content of a location reference allows the location to be presented in a graphical or textual
manner to the end-user (e.g. coloured network graphs) as well as to be used for navigational systems purposes.
3.1.3
Location Referencing Container
concept applied to the grouping of all the Location Referencing elements, of a TPEG-Message,
together in one place
2 © ISO 2015 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/TS 21219-18:2015(E)
3.2 Abbreviated terms
ADC Application Data Container
AID TPEG Application ID
CEN Comité Européen de Normalization
EBU European Broadcasting Union
LRC Location Referencing Container
MMC Message Management Container
OSI Open Systems Interconnection
SSF TPEG Specification: Syntax, Semantics and Framing Structures
TPEG Transport Protocol Expert Group
TTI Traffic and Traveller Information
UML Unified Modelling Language
XML Extensible Markup Language
XSD XML Schema Definition
4 Application specific constraints
Ordered Components
TPEG-TFP requires a fixed order of TPEG components. The order for the TFP message component is
shown in Figure 1; the first component shall be the Message Management Container. This shall be the only
component if the message is a cancellation message. Otherwise, the MMC component shall be followed by
the Application Data Container component which includes the traffic flow information. This shall be followed
by the Location Referencing Container component, if the LRC is present in this message (see also 6.1).
Figure 1 — Composition of TPEG messages
Extendibility
The requirement of a fixed component order does not affect the extension of TFP. Future application
extensions may insert new components or may replace existing components by new ones without losing
backward compatibility. That means a TFP decoder shall be able to detect and skip unknown components.
© ISO 2015 – All rights reserved 3
---------------------- Page: 10 ----------------------
ISO/TS 21219-18:2015(E)
For reasons of efficiency some data structures of TFP which may potentially require extensions in future
are defined as TPEG DataStructures though these structures are not extensible in a backward compatible
way. To ensure extensibility dedicated extension components are added to these DataStructures which
may be used for future TFP extensions of TFP (DataStructures ‘FlowVectorSection’, ‘StatusParameters’,
‘Restrictions’, ‘StatisticalParameters’, see also 6.1).
TPEG Service Component Frame
TFP makes use of the “Service Component Frame with dataCRC, groupPriority, and messageCount”
according to ISO/TS 21219-5.
Version number signalling
Version numbering is used to track the separate versions of an application through its development and
deployment. The differences between these versions may have an impact on client devices.
For services basing on this TFP specification the following version numbers shall be signalled in the SNI:
— major version number 1
— minor version number 0
Application ID (AID)
The TFP application ID is assigned by ISO/TS 18234-1:2013. As this document requires some time for
update with the recent AIDs it may not include all assigned AIDs. In this case, please contact TISA for
further information.
4 © ISO 2015 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/TS 21219-18:2015(E)
5 TFP Structure
Figure 2 — UML Class Model of TPEG-TFP
6 TFP Message components
6.1 TFPMessage
A ‘TFPMessage’ component is the top container of a TFP message. It contains all information about a
particular part of the network, for example the traffic state for a road segment.
The traffic flow content of a TFPMessage is typically highly dynamic while the affected road stretch
defined by the Location Referencing Container (LRC) shall remain static during the life cycle of a
message. Thus, partial message management (ISO/TS 21219-6) may be applied to update the traffic
flow states of a message frequently whereas the LRC may be repeated with a longer repetition interval.
Accordingly, a TFP message can include alternatively
— One MMC only in case of a cancellation message (ISO/TS 21219-6)
— One MMC, one or several ADCs and one LRC in case of monolithic message management
(ISO/TS 21219-6):
© ISO 2015 – All rights reserved 5
---------------------- Page: 12 ----------------------
ISO/TS 21219-18:2015(E)
— Partial message management (ISO/TS 21219-6):
— One MMC only, including the multipart message directory
— One MMC and one or several ADCs
— One MMC and one LRC
TFP provides three methods for the representation of current and predicted traffic flow states which
may be used alternatively, i.e. just one method shall be applied within one TFP message:
— Flow-Polygon-Method: The traffic flow is modelled by a number of spatial/temporal
‘FlowPolygonObjects’ (see description of component ‘FlowPolygonObject’, 6.5).
— FlowStatus-Method: A flow status applied to the overall road stretch defined by the LRC of the
message (see description of component ‘FlowStatus’, 6.7). A TFP message using this method and
which is not a cancellation message shall contain exactly one ‘FlowStatus’ container.
— Flow-Matrix-Method: The road stretch is divided into sections each with a homogenous flow state,
thus building a ‘FlowVector’. A ‘FlowMatrix’ consists of one or several FlowVectors for dedicated
temporal intervals, e.g. with one FlowVector for the current flow status and another one for
prognosis in 15 min (see description of components ‘FlowMatrix’, 6.8). A TFP message using this
method and which is not a cancellation message shall contain exactly one ‘FlowMatrix’ container.
To minimize the length of TFP messages the spatial positions of the Flow-Matrix and Flow-Polygon
methods are coded by spatial offsets to the location reference in the LRC. These offsets shall be calculated
in upstream direction to the end of the road stretch as defined by the location reference of the message
(see also 6.3). The location reference in the LRC shall cover the entire road stretch required for this TFP
message. The Flow-Matrix method allows also the usage of relative offsets (see 6.8).
The attributes of the ‘TFPMessage’ component are listed hereunder:
Multiplic-
Name Type Description
ity
Ordered Components
mmc MessageManagementContainer 1 Message Management Container
(external)
method Component TFPMethod 0.* Tra
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.