ISO/TS 18234-8:2012

TECHNICAL ISO/TS
SPECIFICATION 18234-8
First edition
10-01-2012
Intelligent transport systems — Traffic
and travel information via transport
protocol experts group, generation 1
(TPEG1) binary data format —
Part 8:
Congestion and Travel Time
application (TPEG1-CTT)
Systèmes intelligents de transport — Informations sur le trafic et le
tourisme via les données de format binaire du groupe d’experts du
protocole de transport, génération 1 (TPEG1) —
Partie 8: Application bouchons et temps de voyage (TPEG1-CTT)
Reference number
©
ISO 2012
© ISO 2012
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any
means, electronic or mechanical, including photocopying and microfilm, without permission in writing 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 2012 – All rights reserved

Contents Page
Foreword .iv
Introduction .vi
1 Scope . 1
2 Conformance . 1
3 Normative references . 1
4 Terms and definitions . 1
5 Abbreviated terms . 3
6 Definitions . 5
6.1 General . 5
6.2 Message Management . 5
6.3 Locations - Abbreviation: Loc . 5
7 CTT Application Overview . 6
7.1 Introduction . 6
7.2 TPEG-Message Concept . 7
7.3 Elements of TPEG Congestion and Travel Time . 8
7.4 Message Management . 8
7.5 Status Description . 9
7.6 Location Referencing . 9
8 CTT Container .10
8.1 Structure of CTT Message .10
8.2 CTT Application Component Frame .10
9 Message Management Container .11
9.1 Mandatory Elements .11
9.2 Date and Time Elements .11
9.3 Coding of Message Management Container .12
10 Status Container .13
10.1 Status Description .13
10.2 Coding of CTT Information Container.13
11 TPEG CTT Tables .16
11.1 Congestion Type Table .16
11.2 Congestion Tendency Table .16
Annex A (informative) Conversion formulae .18
Bibliography .20
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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International
Standards adopted by the technical committees are circulated to the member bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the member bodies
casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of document:
— an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical
experts in an ISO working group and is accepted for publication if it is approved by more than 50 % of
the members of the parent committee casting a vote;
— an ISO Technical Specification (ISO/TS) represents an agreement between the members of
a technical committee and is accepted for publication if it is approved by 2/3 of the members of the
committee casting a vote.
An ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed for
a further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or
ISO/TS is confirmed, it is reviewed again after a further three years, at which time it must either be
transformed into an International Standard or be withdrawn.
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.
ISO/TS 18234-8 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
ISO/TS 18234 consists of the following parts, under the general title 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)
— Part 2: Syntax, Semantics and Framing Structure (SSF)
— Part 3: Service and Network Information (SNI) application
— Part 4: Road Traffic Message (RTM) application
— Part 5: Public Transport Information (PTI) application
— Part 6: Location referencing applications
1)
— Part 7: Parking Information (TPEG1-PKI)
— Part 8: Congestion and travel time application (TPEG1-CTT)
2)
— Part 9: Traffic event compact (TPEG1-TEC)
1) To be published.
2) To be published.
iv © ISO 2012 – All rights reserved

3)
— Part 10: Conditional access information (TPEG1-CAI)
4)
— Part 11: Location Referencing Container (TPEG1-LRC)
3) To be published.
4) To be published.
Introduction
TPEG technology uses a byte-oriented stream format, which may be carried on almost any digital bearer
with an appropriate adaptation layer. TPEG-messages are delivered from service providers to end-users,
and are used to transfer application data from the database of a service provider to a user’s equipment.
This Technical Specification describes the Congestion and Travel Time application in detail.
TPEG1-CTT is one of several applications required to provide a fully comprehensive traffic and travel
information service, for example a service is likely to need public transport information, parking
information and weather information. These are or will be the subject of other TPEG-application
specifications.
TPEG1-CTT has been derived from earlier work, named “idio” via the FM data broadcasting system,
DARC. The “idio” is the TTI service which was officially launched starting in 2001 all over South Korea.
The TPEG1-CTT has become the most popular service of the many applications of DMB, after being tested
and proven via both the terrestrial and satellite DMB (Digital Multimedia Broadcasting) networks.
The Broadcast Management Committee of the European Broadcast Union (EBU) established the
B/TPEG project group in autumn 1997 with the mandate to develop, as soon as possible, a new protocol
for broadcasting traffic and travel-related information in the multimedia environment. The TPEG
technology, its applications and service features are 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.
One year later in December 1998, the B/TPEG group produced its first public specifications. Two
documents were released. ISO/TS 18234-2,TPEG-SSF, describes the syntax, semantics and framing
structure which are used for all TPEG applications. ISO/TS 18234-4, TPEG-RTM describes the first
application for Road Traffic Messages.
ISO/TC 204/WG 10, established a project group comprising the members of B/TPEG and they have
continued the work concurrently since March 1999. Since then two further parts have been developed
to make the initial complete set of four parts, enabling the implementation of a consistent service.
ISO/TS 18234-3, TPEG-SNI describes the Service and Network Information Application, which is likely
to be used by all service implementations to ensure appropriate referencing from one service source
to another. ISO/TS 18234-1, TPEG-INV, completed the work, by describing the other parts and their
relationships; it also contains the application IDs used within the other parts.
In April 2000, the B/TPEG group released revised Parts 1 to 4, which had all been reviewed and updated
in light of the initial implementation results. Thus, a consistent suite of specifications, ready for wide-
scale implementation, was submitted to the ISO commenting process.
In November 2001, after extensive response to the comments received and from many internally
suggested improvements, all four parts were completed for the next stage: the Parallel Formal Vote. But
a major step forward has been to develop the so-called TPEG-Loc location referencing method, which
enables both map-based TPEG-decoders and non map-based ones to deliver either map-based location
referencing or human readable information. ISO/TS 18234-6, TPEG-Loc, is now a separate specification
and is used in association with the other parts of ISO/TS 18234 to provide comprehensive location
referencing. Additionally, ISO/TS 18234-5, the Public Transport Information Application (TPEG-PTI)
has been developed and been through the commenting process.
This Technical Specification provides a full specification for the Congestion and Travel Time application.
Today, traffic congestion has become a serious problem in urban areas. Some traffic congestion is
considered to be caused by drivers who do not have access to traffic information. Therefore, timely
provision of congestion and travel time messages to these drivers could decrease traffic congestion.
TPEG Congestion and Travel Time Messages are designed to provide information to various kinds of
receivers using digital broadcasting and Internet technologies. A Congestion and Travel Time Message
may be presented to the user in many different ways, including text, audio, or graphically using standard
vi © ISO 2012 – All rights reserved

formats application which is designed to allow the efficient and language independent delivery of road
information directly from service provider to end-users. The information provided relates to event and
some status information on the road network and on associated infrastructure affecting a road journey.
For example, limited information about abnormal operation of links in the network may be included, e.g.
ferries, lifting-bridges.
The term “application” is used in TPEG specifications to describe specific applications, such as in this
case the Congestion and Travel Time application, which comprises three information containers: the
Message Management Container, the Application Event Container and the TPEG-Location Container.
The first two Containers are fully described herein and the TPEG-Location Container is described in
ISO/TS 18234-6.
Each TPEG application (e.g. TPEG1-CTT) is assigned a unique number, called the Application Identification
(AID). An AID is defined whenever a new application is developed. The AID is used within the TPEG-
Service and Network Information Application (ISO/TS 18234-3 to indicate how to process TPEG content
and allows routing of data to an appropriate application decoder.
AID = 0004 is assigned to the TPEG-Congestion Travel Time Message application described in this
Technical Specification.
A hierarchical methodology has been developed to allow the creation of messages from a set of TPEG1-
CTT tables, which are essentially word oriented and cover most needs.
TECHNICAL SPECIFICATION ISO/TS 18234-8:2012(E)
Intelligent transport systems — Traffic and travel
information via transport protocol experts group,
generation 1 (TPEG1) binary data format —
Part 8:
Congestion and Travel Time application (TPEG1-CTT)
1 Scope
This Technical Specification establishes a method for delivering Congestion and Travel Time Messages
within a TPEG service.
2 Conformance
The TPEG1-CTT has been tested and proven via both terrestrial and satellite Digital Multimedia
Broadcasting (DMB) networks since 2006 in Korea.
3 Normative references
The following referenced documents are indispensable for the application 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 18234-2, Traffic and Travel Information (TTI) — TTI via Transport Protocol Expert Group (TPEG)
data-streams — Part 2: Syntax, Semantics and Framing Structure (SSF)
ISO/TS 18234-3, Traffic and Travel Information (TTI) — TTI via Transport Protocol Expert Group (TPEG)
data-streams — Part 3: Service and Network Information (SNI) application
4 Terms and definitions
For the purposes of this Technical Specification, the following terms and definitions apply.
NOTE Definitions in this Technical Specification are in some cases derived from definitions found in the
DATEX Data Dictionary (ENV 13106). TPEG-RTM is completely focused on delivering messages to end-users.
For this key operational reason some definitions have a different meaning from that found in the DATEX Data
Dictionary. These differences are noted in a note to the term.
4.1
cross reference information
CRI
pointer to one or more messages in the same, or another TPEG service
4.2
event description
EVE
part of a message describing an event, unplanned or planned, affecting the road or transport network,
or status information, including qualifiers and quantifiers
NOTE This definition varies from the DATEX Data Dictionary definition (ENV 13106).
EXAMPLE The transport network in the case of a ferry carrying vehicles between parts of the road network.
4.3
location referencing
method for referencing locations to facilitate the exchange of location related information between
different systems
NOTE See ISO/TS 18234-6 for full details of the location referencing container explanations.
4.4
message
collection of coherent information sent through an information channel which describes an event or a
collection of related events, or status information and including message management information
NOTE The latter is contained in the message header.
4.5
message expiry time
MET
date and time in accordance with ISO 8601 when the message should be deleted from all TPEG-decoders
NOTE Used for message management purposes.
4.6
message generation time
MGT
date and time stamp in accordance with ISO 8601 originated at the actual time and point of message
generation
NOTE Used for message management purposes.
4.7
message identifier
MID
unique identifier for a sequence of versions of one message relating to a particular event of a particular
service component
4.8
position
where an event has taken place in relation to the road
NOTE The driving lanes are numbered according to the usual local practice, i.e. driving lane 1 is the lane
nearest to the hard shoulder. In countries which drive on the left, driving lanes are hence numbered from left-to-
right, and in countries driving on the right, from right-to-left.
EXAMPLE Driving lane 1, hard shoulder, central reservation.
4.9
severity factor
SEV
amount of disruption to traffic likely to be caused by a particular event
NOTE This definition varies from the DATEX Data Dictionary definition (ENV 13106).
4.10
start time
STA
date and time in accordance with ISO 8601 at which an event, or status information, began or is
scheduled to begin
NOTE 1 Used for presentation to the end-user.
NOTE 2 This definition varies from the DATEX Data Dictionary definition (ENV 13106).
2 © ISO 2012 – All rights reserved

4.11
status
characteristic of an element of the transport system for which a value can be established at all times
NOTE 1 This relates to an information stream.
NOTE 2 Values can be normal or deviating from normal.
4.12
stop time
STO
date and time in accordance with ISO 8601 at which an event, or status information, ended or is
scheduled to end
NOTE 1 Used for presentation to the end-user.
NOTE 2 This definition varies from the DATEX Data Dictionary definition (ENV 13106).
4.13
time schedule information
TSI
information about the time schedule for repetitive events within the start and stop time
4.14
unverified information
UNV
information indicating that a message includes information from an unverified source
4.15
version number
VER
serial number to distinguish successive messages having a particular message identifier
NOTE Version numbers are used incrementally, allowing the progress of an event to be tracked from first
notification (VER = 0), through updates, to eventual cancellation (VER = 255).
5 Abbreviated terms
For the purposes of this Technical Specification, the following abbreviated terms apply.
AID Application Identification
BPN Broadcast, Production and Networks (an EBU document publishing number system)
B/TPEG Broadcast/TPEG (the EBU project group name for the specification drafting group)
CEN Comité Européen de Normalisation
CRI Cross Reference Information
DAB Digital Audio Broadcasting
DMB Digital Multimedia Broadcasting
DVB Digital Video Broadcasting
EBU European Broadcasting Union
ETSI European Telecommunications Standards Institute
EVE Event Description
ILOC Intersection location
INV Introduction, Numbering and Versions (see ISO/TS 18234-1)
IPR Intellectual Property Right(s)
ISO International Organization for Standardization
MET Message Expiry Time
MGT Message Generation Time
MID Message Identifier
OSI Open Systems Interconnection
PTI Public Transport Information (see ISO/TS 18234-5)
RDS-TMC Radio Data System – Traffic Message Channel
RFU Reserved for future use (not necessarily abbreviated)
RTM Road Traffic Message application
SEV Severity Factor
SNI Service and Network Information application (see ISO/TS 18234-3)
SSF Syntax, Semantics and Framing Structure (see ISO/TS 18234-2)
STA Start Time
STO Stop Time
TPEG Transport Protocol Experts Group
TSI Time Schedule Information
TTI Traffic and Travel Information
UAV Unassigned value
4 © ISO 2012 – All rights reserved

6 Definitions
6.1 General
Definitions in this Technical Specification are in some cases derived from definitions found in the DATEX
Data Dictionary.
6.1.1 Message
A collection of coherent information sent through an information channel.
Describes an event or a collection of related events, or status information and including message
management information. The latter is contained in the message header.
6.1.2 Status
Characteristics of an element of the transport system for which at all times a value can be established.
Status relates to an information stream. Values can be normal or deviating from normal.
6.2 Message Management
6.2.1 Message Identification – Abbreviation: MID
Message Identification (MID) is one of the message identifiers in relation to each event of service components.
A unique identifier for a sequence of versions of one message relates to a particular event of a particular
service component.
6.2.2 Version Number - Abbreviation: VER
Version number (VER) means the sequential numbers to identify consecutive messages with the same
MID. When an event occurs, VER is used in such a manner that is to be increased sequentially from the
initial MID of 0 in accordance with updates of information.
Serial number is used to distinguish successive messages having a particular Message Identifier. Version
numbers are used incrementally allowing the progress of an event to be tracked from first notification
(VER = 0), through updates, to eventual cancellation (VER = 255).
This definition varies from the DATEX Data Dictionary definition.
6.2.3 Message generation data and time – Abbreviati
...