ISO/TS 21219-19:2016
(Main)Intelligent transport systems — Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) — Part 19: Weather information (TPEG2-WEA)
Intelligent transport systems — Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) — Part 19: Weather information (TPEG2-WEA)
ISO/TS 21219-19:2016 defines the TPEG Weather (WEA) application for reporting weather information for travellers. It provides general weather-related information to all travellers and is not limited to a specific mode of transportation. This application does not provide specific weather-related safety warnings to drivers; these are provided as Safety Related Messages as part of the TPEG2-TEC application. The WEA application provides weather-related forecasts and status information over multiple time periods and for multiple, possibly linked, geographical areas. NOTE The presentation of the information is dependent of the specific HMI of the receiving device. ISO/TS 21219-19 :2016, therefore, does not define any prerequisites for the HMI of the device.
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 19: Renseignements météorologiques (TPEG2-WEA)
General Information
Relations
Buy Standard
Standards Content (Sample)
TECHNICAL ISO/TS
SPECIFICATION 21219-19
First edition
2016-06-15
Intelligent transport systems —
Traffic and travel information (TTI)
via transport protocol experts group,
generation 2 (TPEG2) —
Part 19:
Weather information (TPEG2-WEA)
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 19: Renseignements météorologiques (TPEG2-WEA)
Reference number
ISO/TS 21219-19:2016(E)
©
ISO 2016
---------------------- Page: 1 ----------------------
ISO/TS 21219-19:2016(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2016, Published in Switzerland
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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2016 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/TS 21219-19:2016(E)
Contents Page
Foreword .v
Introduction .vii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Application specific constraints . 3
5.1 Application identification . 3
5.2 Version number signalling . 3
5.3 Ordered components . 3
5.4 Extendibility . 3
5.5 TPEG service component frame . 4
6 WEA structure . 4
7 WEA message components . 4
7.1 WeatherMessage . 6
7.2 WeatherInformation . 6
7.3 WeatherReport . 7
7.4 WeatherItem . 7
7.5 WeatherStatistics . 8
7.6 WeatherWarning . 9
7.7 AltitudeElements .10
7.8 OutlookTrend .10
7.9 ReportLinkInfo .10
7.10 WebContentLinks.11
7.11 MMCSwitch .11
7.12 MMCMessagePartLink .11
7.13 MMCMasterMessageLink .11
7.14 MessageManagementContainerLink.12
7.15 LocationReferencingContainerLink .12
8 WEA datatypes .12
8.1 LinkedMessage .12
8.2 Element.12
9 WEA tables .13
9.1 wea000:ReportType .13
9.2 wea001:Period .13
9.3 wea002:TrendItem .15
9.4 wea003:Direction .15
9.5 wea004:PressureTendency .16
9.6 wea005:Visibility .16
9.7 wea006:SeaState .17
9.8 wea007:PollenCount .17
9.9 wea008:AirQuality .17
9.10 wea009:WarningLevel.18
9.11 wea010:UVIndex .18
9.12 wea011:GeoSignificance .19
9.13 wea012:WindDirectionTrend .19
9.14 wea013:WindSpeedTrend .20
9.15 wea014:ContentType .20
9.16 wea099:ElementSubTable .20
9.17 wea100:ElementType .20
9.18 wea101:RainElements .21
© ISO 2016 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/TS 21219-19:2016(E)
9.19 wea102:SnowElements .21
9.20 wea103:SleetHailElements .22
9.21 wea104:WindElements .22
9.22 wea105:StormElements .23
9.23 wea106:FogElements .24
9.24 wea107:FrostElements .24
9.25 wea108:SunshineCloudElements .24
9.26 wea109:TemperatureElements .25
9.27 wea110:HazardElements .25
9.28 wea200:ElementQualifier.26
9.29 wea201:ElementQualifierProbability .27
Annex A (normative) TPEG application, TPEG-binary representation .28
Annex B (normative) TPEG application, TPEG-ML representation.37
Annex C (informative) Worked examples .48
Annex D (informative) Suggested translation between WEA table codes and WMO SYNOP
weather observation codes .53
Bibliography .60
iv © ISO 2016 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/TS 21219-19:2016(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 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 experts group, generation 2 (TPEG2):
— Part 1: Introduction, numbering and versions
— Part 2: UML modelling rules
— Part 3: UML to binary conversion rules
— Part 4: UML to XML conversion rules
— Part 5: Service framework
— Part 6: Message management container
— Part 9: Service and network information
— Part 10: Conditional access information
— Part 14: Parking information application
— Part 18: Traffic flow and prediction application
— Part 19: Weather information
The following parts are under preparation:
— Part 15: Traffic event compact
— Part 16: Fuel price information application
© ISO 2016 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/TS 21219-19:2016(E)
The following parts are planned:
— Part 7: Location referencing container
— Part 11: Universal location reference
— Part 21: Geographic location referencing
— Part 22: OpenLR location referencing
— Part 23: Road and multimodal routes application
— Part 24: Light encryption
— Part 25: Electromobility charging infrastructure
vi © ISO 2016 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/TS 21219-19:2016(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
group comprising members of the former EBU B/TPEG and this working group continued development
work. 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
When the Traveller Information Services Association (TISA), derived from former Forums, was
inaugurated in December 2007, TPEG development was taken over by TISA and continued in the TPEG
applications working group.
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.
© ISO 2016 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO/TS 21219-19:2016(E)
TPEG2 has a three container conceptual structure: Message Management (ISO/TS 21219-6), Application
(many ISO/TS 21219 parts) and Location Referencing (ISO/TS 21219-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 (ISO/TS 21219-1), TPEG2-UML (ISO/TS 21219-2), TPEG2-UBCR
(ISO/TS 21219-3), TPEG2-UXCR (ISO/TS 21219-4), TPEG2-SFW (ISO/TS 21219-
5), TPEG2-MMC (ISO/TS 21219-6), TPEG2-LRC (ISO/TS 21219-7);
Special applications: TPEG2-SNI (ISO/TS 21219-9), TPEG2-CAI (ISO/TS 21219-10);
Location referencing: TPEG2-ULR (ISO/TS 21219-11), TPEG2-GLR (ISO/TS 21219-21), TPEG2-OLR
(ISO/TS 21219-22);
Applications: TPEG2-PKI (ISO/TS 21219-14), TPEG2-TEC (ISO/TS 21219-15), TPEG2-FPI (ISO/
TS 21219-16), TPEG2-TFP (ISO/TS 21219-18), TPEG2-WEA (ISO/TS 21219-19),
TPEG2-RMR (ISO/TS 21219-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 reference:
SP13002/1.1/001
viii © ISO 2016 – All rights reserved
---------------------- Page: 8 ----------------------
TECHNICAL SPECIFICATION ISO/TS 21219-19:2016(E)
Intelligent transport systems — Traffic and travel
information (TTI) via transport protocol experts group,
generation 2 (TPEG2) —
Part 19:
Weather information (TPEG2-WEA)
1 Scope
This part of ISO/TS 21219 defines the TPEG Weather (WEA) application for reporting weather
information for travellers. It provides general weather-related information to all travellers and is not
limited to a specific mode of transportation.
This application does not provide specific weather-related safety warnings to drivers; these are
provided as Safety Related Messages as part of the TPEG2-TEC application.
The WEA application provides weather-related forecasts and status information over multiple time
periods and for multiple, possibly linked, geographical areas.
NOTE The presentation of the information is dependent of the specific HMI of the receiving device. This part
of ISO/TS 21219, therefore, does not define any prerequisites for the HMI of the device.
2 Normative references
The following documents are referred to in the text in such a way that some or all of 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 21219-5, Intelligent transport systems — Traffic and travel information (TTI) via transport
protocol experts group, generation 2 (TPEG2) — Part 5: Service framework
ISO/TS 21219-6, Intelligent transport systems — Traffic and travel information via transport protocol
experts group, generation 2(TPEG2) — Part 6: Message management container
ISO/TS 21219-9, Intelligent transport systems — Traffic and travel information via transport protocol
experts group, generation 2 (TPEG2) — Part 9: Service and network information
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
service
collection of different information streams (applications) logically bound together and delivered from a
service provider to the end user
© ISO 2016 – All rights reserved 1
---------------------- Page: 9 ----------------------
ISO/TS 21219-19:2016(E)
3.2
service component
information stream (application) that is part of a service (3.1)
Note 1 to entry: A TPEG stream is logically divided into parts known as service components. Each service
component carries an application instance. A service component is effectively a “channel” within the multiplex
of a TPEG stream. Each stream comprises a number of these “channels” which are identified by the component
identifier in TPEG2-SFW and linked to the COID and AID in the TPEG2-SNI application.
3.3
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.4
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.5
location referencing container
concept applied to the grouping of all the location referencing (3.4) elements, of a TPEG-Message,
together in one place
4 Abbreviated terms
ACID Application and Content Identifier
ADC Application Data Container
CEN Comité Européen de Normalization
EBU European Broadcasting Union
LRC Location Reference Container
MMC Message Management Container
n.a. Not available
OSI Open Systems Interconnection
SFW TPEG Service Framework: Modelling and Conversion Rules
TISA Traveller Information Services Association
TPEG Transport Protocol Expert Group
TTI Traffic and Traveller Information
UML Unified Modelling Language
TEC Traffic Event Compact
WEA TPEG Weather
WMO World Meteorological Organization
2 © ISO 2016 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/TS 21219-19:2016(E)
5 Application specific constraints
5.1 Application identification
The word “application” is used in the TPEG specifications to describe specific subsets of the TPEG
structure. An application defines a limited vocabulary for a certain type of messages, for example,
parking information or road traffic information. Each TPEG application is assigned a unique number,
called the Application IDentification (AID). An AID is defined whenever a new application is developed
and these are all listed in TPEG2-MMC (ISO/TS 21219-6).
The application identification number is used within the TPEG2-SNI (ISO/TS 21219-9) application to
indicate how to process TPEG content and facilitates the routing of information to the appropriate
application decoder.
5.2 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.
The version numbering principle is defined in TPEG2-INV.
Table 1 shows the current version numbers for signalling WEA within the SNI application.
Table 1 — Current version numbers for signalling of WEA
Major version number 1
Minor version number 1
5.3 Ordered components
TPEG2-WEA requires a fixed order of TPEG components. The order for the WEA 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 one or more Application Data Container component(s) which includes the application-
specific information.
Figure 1 — Composition of TPEG messages
5.4 Extend
...
TECHNICAL ISO/TS
SPECIFICATION 21219-19
First edition
Intelligent transport systems —
Traffic and travel information via
transport protocol experts group,
generation 2 (TPEG2) —
Part 19:
Weather information (TPEG2-WEA)
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 19: Renseignements météorologiques (TPEG2-WEA)
PROOF/ÉPREUVE
Reference number
ISO/TS 21219-19:2016(E)
©
ISO 2016
---------------------- Page: 1 ----------------------
ISO/TS 21219-19:2016(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2016, Published in Switzerland
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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2016 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/TS 21219-19:2016(E)
Contents Page
Foreword .v
Introduction .vii
1 Scope . 1
2 Terms and definitions . 1
3 Abbreviated terms . 2
4 Application specific constraints . 2
4.1 Application identification . 2
4.2 Version number signalling . 2
4.3 Ordered components . 3
4.4 Extendibility . 3
4.5 TPEG service component frame . 3
5 WEA structure . 4
6 WEA message components . 4
6.1 WeatherMessage . 6
6.2 WeatherInformation . 6
6.3 WeatherReport . 7
6.4 WeatherItem . 7
6.5 WeatherStatistics . 8
6.6 WeatherWarning . 9
6.7 AltitudeElements .10
6.8 OutlookTrend .10
6.9 ReportLinkInfo .11
6.10 WebContentLinks.11
6.11 MMCSwitch .11
6.12 MMCMessagePartLink .11
6.13 MMCMasterMessageLink .11
6.14 MessageManagementContainerLink.12
6.15 LocationReferencingContainerLink .12
7 WEA datatypes .12
7.1 LinkedMessage .12
7.2 Element.12
8 WEA tables .13
8.1 wea000:ReportType .13
8.2 wea001:Period .13
8.3 wea002:TrendItem .15
8.4 wea003:Direction .16
8.5 wea004:PressureTendency .16
8.6 wea005:Visibility .17
8.7 wea006:SeaState .17
8.8 wea007:PollenCount .17
8.9 wea008:AirQuality .18
8.10 wea009:WarningLevel.18
8.11 wea010:UVIndex .19
8.12 wea011:GeoSignificance .19
8.13 wea012:WindDirectionTrend .20
8.14 wea013:WindSpeedTrend .20
8.15 wea014:ContentType .20
8.16 wea099:ElementSubTable .21
8.17 wea100:ElementType .21
8.18 wea101:RainElements .21
8.19 wea102:SnowElements .22
© ISO 2016 – All rights reserved PROOF/ÉPREUVE iii
---------------------- Page: 3 ----------------------
ISO/TS 21219-19:2016(E)
8.20 wea103:SleetHailElements .22
8.21 wea104:WindElements .23
8.22 wea105:StormElements .24
8.23 wea106:FogElements .24
8.24 wea107:FrostElements .25
8.25 wea108:SunshineCloudElements .25
8.26 wea109:TemperatureElements .26
8.27 wea110:HazardElements .26
8.28 wea200:ElementQualifier.27
8.29 wea201:ElementQualifierProbability .29
Annex A (normative) TPEG application, TPEG-binary representation .30
Annex B (normative) TPEG application, TPEG-ML representation .40
Annex C (informative) Worked examples .51
Annex D (informative) Suggested translation between WEA table codes and WMO SYNOP
weather observation codes .56
Bibliography .63
iv PROOF/ÉPREUVE © ISO 2016 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/TS 21219-19:2016(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 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 experts group, generation 2 (TPEG2):
— Part 1: Introduction, numbering and versions
— Part 2: UML modelling rules
— Part 3: UML to binary conversion rules
— Part 4: UML to XML conversion rules
— Part 5: Service framework
— Part 6: Message management container
— Part 10: Conditional access information
— Part 18: Traffic flow and prediction application
— Part 19: Weather information
The following parts are under preparation:
— Part 9: Service and network information
— Part 14: Parking information
— Part 15: Traffic event compact
— Part 16: Fuel price information and availability application
© ISO 2016 – All rights reserved PROOF/ÉPREUVE v
---------------------- Page: 5 ----------------------
ISO/TS 21219-19:2016(E)
The following parts are planned:
— Part 7: Location referencing container
— Part 11: Universal location reference
— Part 21: Geographic location referencing
— Part 22: OpenLR location referencing
— Part 23: Road and multimodal routes application
— Part 24: Light encryption
— Part 25: Electromobility information
vi PROOF/ÉPREUVE © ISO 2016 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/TS 21219-19:2016(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
group comprising members of the former EBU B/TPEG and this working group continued development
work. 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
When the Traveller Information Services Association (TISA), derived from former Forums, was
inaugurated in December 2007, TPEG development was taken over by TISA and continued in the TPEG
applications working group.
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.
© ISO 2016 – All rights reserved PROOF/ÉPREUVE vii
---------------------- Page: 7 ----------------------
ISO/TS 21219-19:2016(E)
TPEG2 has a three container conceptual structure: Message Management (ISO/TS 21219-6), Application
(many ISO/TS 21219 parts) and Location Referencing (ISO/TS 21219-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 (ISO/TS 21219-1), TPEG2-UML (ISO/TS 21219-2), TPEG2-UBCR
(ISO/TS 21219-3), TPEG2-UXCR (ISO/TS 21219-4), TPEG2-SFW (ISO/TS 21219-
5), TPEG2-MMC (ISO/TS 21219-6), TPEG2-LRC (ISO/TS 21219-7);
Special applications: TPEG2-SNI (ISO/TS 21219-9), TPEG2-CAI (ISO/TS 21219-10);
Location referencing: TPEG2-ULR (ISO/TS 21219-11), TPEG2-ETL (ISO/TS 21219-20), TPEG2-GLR
(ISO/TS 21219-21), TPEG2-OLR (ISO/TS 21219-22);
Applications: TPEG2-PKI (ISO/TS 21219-14), TPEG2-TEC (ISO/TS 21219-15), TPEG2-FPI (ISO/
TS 21219-16), TPEG2-TFP (ISO/TS 21219-18), TPEG2-WEA (ISO/TS 21219-19),
TPEG2-RMR (ISO/TS 21219-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 reference:
SP13002/1.1/001
viii PROOF/ÉPREUVE © ISO 2016 – All rights reserved
---------------------- Page: 8 ----------------------
TECHNICAL SPECIFICATION ISO/TS 21219-19:2016(E)
Intelligent transport systems — Traffic and travel
information via transport protocol experts group,
generation 2 (TPEG2) —
Part 19:
Weather information (TPEG2-WEA)
1 Scope
This part of ISO/TS 21219 defines the TPEG Weather (WEA) application for reporting weather
information for travellers. It provides general weather-related information to all travellers and is not
limited to a specific mode of transportation.
This application does not provide specific weather-related safety warnings to drivers; these are
provided as Safety Related Messages as part of the TPEG2-TEC application.
The WEA application provides weather-related forecasts and status information over multiple time
periods and for multiple, possibly linked, geographical areas.
NOTE The presentation of the information is dependent of the specific HMI of the receiving device. This part
of ISO/TS 21219, therefore, does not define any prerequisites for the HMI of the device.
2 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
2.1
service
collection of different information streams (applications) logically bound together and delivered from a
service provider to the end user
2.2
service component
information stream (application) that is part of a service (2.1)
Note 1 to entry: A TPEG stream is logically divided into parts known as service components. Each service
component carries an application instance. A service component is effectively a “channel” within the multiplex
of a TPEG stream. Each stream comprises a number of these “channels” which are identified by the component
identifier in TPEG2-SFW and linked to the COID and AID in the TPEG2-SNI application.
2.3
message management container
concept applied to the grouping of all message elements including message management information of
a TPEG-Message together in one place
2.4
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.
© ISO 2016 – All rights reserved PROOF/ÉPREUVE 1
---------------------- Page: 9 ----------------------
ISO/TS 21219-19:2016(E)
2.5
location referencing container
concept applied to the grouping of all the location referencing (2.4) elements, of a TPEG-Message,
together in one place
3 Abbreviated terms
For the purposes of this document, the following abbreviated terms apply.
ACID Application and Content Identifier
ADC Application Data Container
CEN Comité Européen de Normalization
EBU European Broadcasting Union
LRC Location Reference Container
MMC Message Management Container
n.a. Not available
OSI Open Systems Interconnection
SFW TPEG Service Framework: Modelling and Conversion Rules
TISA Traveller Information Services Association
TPEG Transport Protocol Expert Group
TTI Traffic and Traveller Information
UML Unified Modelling Language
TEC Traffic Event Compact
WEA TPEG Weather
WMO World Meteorological Organization
4 Application specific constraints
4.1 Application identification
The word “application” is used in the TPEG specifications to describe specific subsets of the TPEG
structure. An application defines a limited vocabulary for a certain type of messages, for example,
parking information or road traffic information. Each TPEG application is assigned a unique number,
called the Application IDentification (AID). An AID is defined whenever a new application is developed
and these are all listed in TPEG2-MMC.
The application identification number is used within the TPEG2-SNI application to indicate how to
process TPEG content and facilitates the routing of information to the appropriate application decoder.
4.2 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.
2 PROOF/ÉPREUVE © ISO 2016 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/TS 21219-19:2016(E)
The version numbering principle is defined in TPEG2-INV.
Table 1 shows the current version numbers for signalling WEA within the SNI application.
Table 1 — Current version numbers for signalling of WEA
Major version number 1
Minor version number 1
4.3 Ordered components
TPEG2-WEA requires a fixed order of TPEG components. The order for the WEA 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 one or more Application Data Container component(s) which includes the application-
specific information.
Figure 1 — Composition of TPEG messages
4.4 Extendibility
The requirement of a fixed component order does not affect the extension of WEA. Future application
extensions may insert new components or may replace existing components by new ones without losing
backward compatibility. That means a WEA decoder shall be able to detect and skip unknown components.
4.5 TPEG service component frame
WEA makes use of the “Service Component Frame with dataCRC and messageCount” according to
TPEG2-SFW.
© ISO 2016 – All rights reserved PROOF/ÉPREUVE 3
---------------------- Page: 11 ----------------------
ISO/TS 21219-19:2016(E)
5 WEA structure
Figure 2 — WEA message structure
6 WEA message components
The WEA application provides a flexible message interface for distribution of weather information.
To enable multiple levels of detail to be signalled, WEA provides two different hierarchal structures to
allow messages to cover multiple geographical areas a
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.