ISO/TS 18234-4:2006
(Main)Traffic and Travel Information (TTI) — TTI via Transport Protocol Expert Group (TPEG) data-streams — Part 4: Road Traffic Message (RTM) application
Traffic and Travel Information (TTI) — TTI via Transport Protocol Expert Group (TPEG) data-streams — Part 4: Road Traffic Message (RTM) application
ISO TS 18234-4:2006 establishes the method of delivering Road Traffic Messages within a TPEG service. The TPEG-RTM application 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, such as ferries, lifting-bridges, etc.
Informations sur le trafic et le tourisme (TTI) — Messages TTI via les flux de données du groupe d'experts du protocole de transport (TPEG) — Partie 4: Application de message de trafic sur route (RTM)
General Information
Relations
Buy Standard
Standards Content (Sample)
TECHNICAL ISO/TS
SPECIFICATION 18234-4
First edition
2006-06-01
Traffic and Travel Information (TTI) — TTI
via Transport Protocol Expert Group
(TPEG) data-streams —
Part 4:
Road Traffic Message (RTM) application
Informations sur le trafic et le tourisme (TTI) — Messages TTI via les
flux de données du groupe d'experts du protocole de transport
(TPEG) —
Partie 4: Application de message de trafic sur route (RTM)
Reference number
©
ISO 2006
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2006
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 2006 – All rights reserved
Contents Page
Foreword. iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions. 2
4 Symbols and abbreviations . 4
5 RTM application overview. 6
5.1 Introduction . 6
5.2 TPEG-message concept. 8
5.3 TPEG-messages delivering additional information . 9
5.4 Elements of a TPEG road traffic message .9
5.5 Message management. 11
5.6 Event description. 13
5.7 Location Referencing . 14
6 RTM container. 14
6.1 Structure of road traffic messages . 14
6.2 Notation . 16
6.3 RTM application component frame. 17
7 Message management container . 18
7.1 Mandatory elements . 18
7.2 Date and time elements. 18
7.3 Severity and reliability elements . 19
7.4 Coding of the message management container. 19
8 Event container . 21
8.1 Event description. 21
8.2 Level one classes . 21
8.3 Coding of the events container . 26
8.4 RTM application primitives . 58
Annex A (informative) Conversion formulae . 96
Bibliography . 98
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 normative 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-4 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
ISO/TS 18234 consists of the following parts, under the general title Traffic and Travel Information (TTI) — TTI
via Transport Protocol Expert Group (TPEG) data-streams:
⎯ Part 1: Introduction, numbering and versions
⎯ 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
iv © ISO 2006 – All rights reserved
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 document describes the Road Traffic Message application in detail.
It should be remembered that the TPEG-RTM has been derived from earlier work that resulted in the
RDS-TMC standards (EN ISO 14819-2). Upon analysis, RDS-TMC can be seen to drift into other application
areas, where it covers a few public transport, parking and weather messages. TPEG-RTM is just 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.
Nevertheless, TPEG-RTM, where reasonable, has included the ability to convey similar content to RDS-TMC,
in order to offer considerable backwards compatibility and the prospect of automatically generating RDS-TMC
messages from TPEG-RTM messages.
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. Part 2 (TPEG-SSF, CEN ISO/TS 18234-2) described the Syntax, Semantics and Framing
structure, which will be used for all TPEG applications. Part 4 (TPEG-RTM, CEN ISO/TS 18234-4) described
the first application, for Road Traffic Messages.
CEN/TC 278/WG 4, in conjunction with 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. Part 3 (TPEG-SNI, CEN ISO/TS 18234-3)) 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. Part 1 (TPEG-INV, CEN ISO/TS 18234-1) 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, all four parts having been reviewed and
updated in the light of initial implementation results. Thus a consistent suite of specifications, ready for wide
scale implementation, was submitted to the CEN/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 in CEN and ISO. 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. Part 6 (TPEG-Loc, CEN ISO/TS 18234-6) is now a separate
specification and is used in association with the other parts of CEN ISO/TS 18234 to provide comprehensive
location referencing. Additionally Part 5, the Public Transport Information Application (TPEG-PTI, CEN
ISO/TS 18234-5), has been developed and been through the commenting process.
This Technical Specification, CEN ISO/TS 18234-4, provides a full specification provides a full specification for
the Road Traffic Message application.
During the development of the TPEG technology a number of versions have been documented and various
trials implemented using various versions of the specifications. At the time of the publication of this Technical
Specification, all parts are fully inter-workable and no specific dependencies exist. This Technical
Specification has the technical version number TPEG-RTM_3.0/003.
vi © ISO 2006 – All rights reserved
TECHNICAL SPECIFICATION ISO/TS 18234-4:2006(E)
Traffic and Travel Information (TTI) — TTI via Transport
Protocol Expert Group (TPEG) data-streams —
Part 4:
Road Traffic Message (RTM) application
1 Scope
This document establishes the method of delivering Road Traffic Messages within a TPEG service. The
TPEG-RTM application 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 net
...
TECHNICAL ISO/TS
SPECIFICATION 18234-4
First edition
2006-06-01
Traffic and Travel Information (TTI) — TTI
via Transport Protocol Expert Group
(TPEG) data-streams —
Part 4:
Road Traffic Message (RTM) application
Informations sur le trafic et le tourisme (TTI) — Messages TTI via les
flux de données du groupe d'experts du protocole de transport
(TPEG) —
Partie 4: Application de message de trafic sur route (RTM)
Reference number
©
ISO 2006
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2006
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 2006 – All rights reserved
Contents Page
Foreword. iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions. 2
4 Symbols and abbreviations . 4
5 RTM application overview. 6
5.1 Introduction . 6
5.2 TPEG-message concept. 8
5.3 TPEG-messages delivering additional information . 9
5.4 Elements of a TPEG road traffic message .9
5.5 Message management. 11
5.6 Event description. 13
5.7 Location Referencing . 14
6 RTM container. 14
6.1 Structure of road traffic messages . 14
6.2 Notation . 16
6.3 RTM application component frame. 17
7 Message management container . 18
7.1 Mandatory elements . 18
7.2 Date and time elements. 18
7.3 Severity and reliability elements . 19
7.4 Coding of the message management container. 19
8 Event container . 21
8.1 Event description. 21
8.2 Level one classes . 21
8.3 Coding of the events container . 26
8.4 RTM application primitives . 58
Annex A (informative) Conversion formulae . 96
Bibliography . 98
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 normative 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-4 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
ISO/TS 18234 consists of the following parts, under the general title Traffic and Travel Information (TTI) — TTI
via Transport Protocol Expert Group (TPEG) data-streams:
⎯ Part 1: Introduction, numbering and versions
⎯ 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
iv © ISO 2006 – All rights reserved
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 document describes the Road Traffic Message application in detail.
It should be remembered that the TPEG-RTM has been derived from earlier work that resulted in the
RDS-TMC standards (EN ISO 14819-2). Upon analysis, RDS-TMC can be seen to drift into other application
areas, where it covers a few public transport, parking and weather messages. TPEG-RTM is just 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.
Nevertheless, TPEG-RTM, where reasonable, has included the ability to convey similar content to RDS-TMC,
in order to offer considerable backwards compatibility and the prospect of automatically generating RDS-TMC
messages from TPEG-RTM messages.
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. Part 2 (TPEG-SSF, CEN ISO/TS 18234-2) described the Syntax, Semantics and Framing
structure, which will be used for all TPEG applications. Part 4 (TPEG-RTM, CEN ISO/TS 18234-4) described
the first application, for Road Traffic Messages.
CEN/TC 278/WG 4, in conjunction with 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. Part 3 (TPEG-SNI, CEN ISO/TS 18234-3)) 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. Part 1 (TPEG-INV, CEN ISO/TS 18234-1) 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, all four parts having been reviewed and
updated in the light of initial implementation results. Thus a consistent suite of specifications, ready for wide
scale implementation, was submitted to the CEN/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 in CEN and ISO. 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. Part 6 (TPEG-Loc, CEN ISO/TS 18234-6) is now a separate
specification and is used in association with the other parts of CEN ISO/TS 18234 to provide comprehensive
location referencing. Additionally Part 5, the Public Transport Information Application (TPEG-PTI, CEN
ISO/TS 18234-5), has been developed and been through the commenting process.
This Technical Specification, CEN ISO/TS 18234-4, provides a full specification provides a full specification for
the Road Traffic Message application.
During the development of the TPEG technology a number of versions have been documented and various
trials implemented using various versions of the specifications. At the time of the publication of this Technical
Specification, all parts are fully inter-workable and no specific dependencies exist. This Technical
Specification has the technical version number TPEG-RTM_3.0/003.
vi © ISO 2006 – All rights reserved
TECHNICAL SPECIFICATION ISO/TS 18234-4:2006(E)
Traffic and Travel Information (TTI) — TTI via Transport
Protocol Expert Group (TPEG) data-streams —
Part 4:
Road Traffic Message (RTM) application
1 Scope
This document establishes the method of delivering Road Traffic Messages within a TPEG service. The
TPEG-RTM application 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 net
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.