Intelligent transport systems — Traffic and travel information via transport protocol experts group, generation 1 (TPEG1) binary data format — Part 9: Traffic event compact (TPEG1-TEC)

ISO/TS 18234-9:2013 defines the TPEG application Traffic Event Compact (TEC). It has been specifically designed to support information about traffic events, e.g. road works, traffic jams. A specific form of traffic event are local hazard warnings, which as safety-related messages, are sent with high priority to assist a driver in encountering dangerous situations (e.g. black-ice, accident behind curves, obstacles on road) unexpectedly.

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 9: Événement trafic compact (TPEG1-TEC)

General Information

Status
Published
Publication Date
09-Oct-2013
Current Stage
9060 - Close of review
Start Date
02-Dec-2027
Ref Project

Relations

Buy Standard

Technical specification
ISO/TS 18234-9:2013 - Intelligent transport systems — Traffic and travel information via transport protocol experts group, generation 1 (TPEG1) binary data format — Part 9: Traffic event compact (TPEG1-TEC) Released:10/10/2013
English language
95 pages
sale 15% off
Preview
sale 15% off
Preview
Technical specification
ISO/TS 18234-9:2013 - Intelligent transport systems -- Traffic and travel information via transport protocol experts group, generation 1 (TPEG1) binary data format
English language
95 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


TECHNICAL ISO/TS
SPECIFICATION 18234-9
First edition
2013-10-15
Intelligent transport systems — Traffic
and travel information via transport
protocol experts group, generation 1
(TPEG1) binary data format —
Part 9:
Traffic event compact (TPEG1-TEC)
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 9: Événement trafic compact (TPEG1-TEC)

Reference number
©
ISO 2013
©  ISO 2013
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 2013 – All rights reserved

Contents Page
Foreword . v
Introduction . vii
1 Scope . 1
2 Normative References . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Application framing and signalling . 2
5.1 Application identification. 2
5.2 Version number signalling . 3
5.3 Application framing . 3
5.4 Application specific constraints . 3
6 Message components . 6
6.1 List of Generic Component Ids . 7
6.2 TECMessage . 7
6.2.1 MessageManagement . 7
6.2.2 Instances of Location Containers . 8
6.2.3 Event . 8
7 Datatypes . 20
7.1 RestrictionType . 20
7.2 SegmentModifier . 21
7.3 TEC Tables . 21
7.3.1 tec001:EffectCode . 21
7.3.2 tec002:CauseCode . 21
7.3.3 tec003:WarningLevel . 23
7.3.4 tec004:LaneRestriction . 24
7.3.5 tec005:AdviceCode . 24
7.3.6 tec006:Tendency . 25
7.3.7 tec007:RestrictionType . 25
7.3.8 tec008:DiversionRoadType . 27
7.3.9 tec009:VehicleType . 27
7.3.10 SubCauseType . 28
7.3.11 SubAdviceType . 39
Annex A (normative) Binary SSF and Data Types . 42
A.1 Conventions and symbols . 42
A.1.1 Conventions . 42
A.1.2 Symbols . 42
A.2 Representation of syntax. 43
A.2.1 General . 43
A.2.2 Data type notation . 43
A.2.3 Application dependent data types . 46
A.2.4 Toolkits and external definition . 50
A.2.5 Application design principles . 51
A.3 TPEG data stream description . 51
A.3.1 Diagrammatic hierarchy representation of frame structure . 51
A.3.2 Syntactical Representation of the TPEG Stream . 52
A.3.3 Description of data on Transport level . 56
A.3.4 Description of data on Service level . 57
A.3.5 Description of data on Service component level . 58
A.4 General binary data types .59
A.4.1 Primitive data types .59
A.4.2 Compound data types .64
A.4.3 Table definitions .67
A.4.4 Tables .69
Annex B (normative) TPEG Message Management Container, MMC (Binary) .85
B.1 Terms and Definitions .85
B.1.1 Message .85
B.1.2 Monolithic Message Management .85
B.1.3 Multi-Part Message Management .85
B.1.4 Top Level Container .85
B.2 Symbols (and abbreviated terms) .85
B.2.1 MMC .85
B.2.2 PKI .85
B.3 Introduction .85
B.4 Message Components .86
B.4.1 MMCTemplate .86
B.4.2 MessageManagementContainer .88
B.4.3 MMCMasterMessage .89
B.4.4 MMCMessagePart .91
B.5 Datatypes .92
B.5.1 MultiPartMessageDirectory .92
B.6 Tables .93
B.6.1 Structure and semantics .93
B.6.2 Indexing .93
B.6.3 Codes, Names and Comments .93
Bibliography .95
iv © ISO 2013 – All rights reserved

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 rev
...


TECHNICAL ISO/TS
SPECIFICATION 18234-9
First edition
2013-10-15
Intelligent transport systems — Traffic
and travel information via transport
protocol experts group, generation 1
(TPEG1) binary data format —
Part 9:
Traffic event compact (TPEG1-TEC)
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 9: Événement trafic compact (TPEG1-TEC)

Reference number
©
ISO 2013
©  ISO 2013
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 2013 – All rights reserved

Contents Page
Foreword . v
Introduction . vii
1 Scope . 1
2 Normative References . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Application framing and signalling . 2
5.1 Application identification. 2
5.2 Version number signalling . 3
5.3 Application framing . 3
5.4 Application specific constraints . 3
6 Message components . 6
6.1 List of Generic Component Ids . 7
6.2 TECMessage . 7
6.2.1 MessageManagement . 7
6.2.2 Instances of Location Containers . 8
6.2.3 Event . 8
7 Datatypes . 20
7.1 RestrictionType . 20
7.2 SegmentModifier . 21
7.3 TEC Tables . 21
7.3.1 tec001:EffectCode . 21
7.3.2 tec002:CauseCode . 21
7.3.3 tec003:WarningLevel . 23
7.3.4 tec004:LaneRestriction . 24
7.3.5 tec005:AdviceCode . 24
7.3.6 tec006:Tendency . 25
7.3.7 tec007:RestrictionType . 25
7.3.8 tec008:DiversionRoadType . 27
7.3.9 tec009:VehicleType . 27
7.3.10 SubCauseType . 28
7.3.11 SubAdviceType . 39
Annex A (normative) Binary SSF and Data Types . 42
A.1 Conventions and symbols . 42
A.1.1 Conventions . 42
A.1.2 Symbols . 42
A.2 Representation of syntax. 43
A.2.1 General . 43
A.2.2 Data type notation . 43
A.2.3 Application dependent data types . 46
A.2.4 Toolkits and external definition . 50
A.2.5 Application design principles . 51
A.3 TPEG data stream description . 51
A.3.1 Diagrammatic hierarchy representation of frame structure . 51
A.3.2 Syntactical Representation of the TPEG Stream . 52
A.3.3 Description of data on Transport level . 56
A.3.4 Description of data on Service level . 57
A.3.5 Description of data on Service component level . 58
A.4 General binary data types .59
A.4.1 Primitive data types .59
A.4.2 Compound data types .64
A.4.3 Table definitions .67
A.4.4 Tables .69
Annex B (normative) TPEG Message Management Container, MMC (Binary) .85
B.1 Terms and Definitions .85
B.1.1 Message .85
B.1.2 Monolithic Message Management .85
B.1.3 Multi-Part Message Management .85
B.1.4 Top Level Container .85
B.2 Symbols (and abbreviated terms) .85
B.2.1 MMC .85
B.2.2 PKI .85
B.3 Introduction .85
B.4 Message Components .86
B.4.1 MMCTemplate .86
B.4.2 MessageManagementContainer .88
B.4.3 MMCMasterMessage .89
B.4.4 MMCMessagePart .91
B.5 Datatypes .92
B.5.1 MultiPartMessageDirectory .92
B.6 Tables .93
B.6.1 Structure and semantics .93
B.6.2 Indexing .93
B.6.3 Codes, Names and Comments .93
Bibliography .95
iv © ISO 2013 – All rights reserved

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 rev
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.