ISO 21219-7:2024
(Main)Intelligent transport systems — Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) — Part 7: Location referencing container (TPEG2-LRC)
Intelligent transport systems — Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) — Part 7: Location referencing container (TPEG2-LRC)
This document establishes the method of signalling the specific location referencing used by all TPEG2 applications that require detailed location information to be delivered to client devices. This document describes the TPEG2-Location Referencing Container (TPEG2-LRC) and shows how it is used to signal which specific location referencing method is in use for a particular TPEG message. It is able to handle location referencing methods that are external to the ISO 21219 series and the internal location referencing methods defined as parts of this series.
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 7: Conteneur de localisation (TPEG2-LRC)
General Information
Relations
Standards Content (Sample)
International
Standard
ISO 21219-7
First edition
Intelligent transport systems —
2024-07
Traffic and travel information (TTI)
via transport protocol experts
group, generation 2 (TPEG2) —
Part 7:
Location referencing container
(TPEG2-LRC)
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 7: Conteneur de localisation (TPEG2-LRC)
Reference number
© ISO 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 3
5 Toolkit specific constraints. 3
5.1 Application identification .3
5.2 Version number signalling .3
5.3 Extendibility .3
6 LRC toolkit structure . 4
7 LRC Toolkit components . 5
7.1 LocationReferencingContainer .5
7.2 Method .6
7.3 DLR1LocationReferenceLink .6
7.4 TMCLocationReferenceLink .6
7.5 KoreanNodeLinkLocationReferenceLink .6
7.6 VICSLinkReferenceLink .6
7.7 ExtendedTMCLocationReferenceLink .6
7.8 GeographicLocationReferenceLink .7
7.9 UniversalLocationReferenceLink .7
7.10 OpenLRLocationReferenceLink .7
7.11 NDSLocationReference . .7
Annex A (normative) TPEG application, TPEG-binary representation . 8
Annex B (normative) TPEG application, tpegML representation.11
Bibliography . 14
iii
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 document 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).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
This first edition cancels and replaces the first edition of ISO/TS 21219-7:2017, which has been technically
revised.
The main changes are as follows:
— the document status has been changed from Technical Specification (TS) to International Standard (IS).
A list of all parts in the ISO 21219 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iv
Introduction
0.1 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 can 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, in conjunction with ISO/TC 204, 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 of parts of the ISO 18234 series to provide location
referencing.
The ISO 18234 series has become known as TPEG Generation 1.
0.2 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
the 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 24530 series (now superseded) had a greater significance
than previously foreseen, especially in the content-generation segment, and that keeping two physical
formats synchronized, 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 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 ISO 21219-2, ISO 21219-3 and ISO 21219-4 and the conversion to two current
physical formats: binary (see Annex A) and XML (see Annex B); others can 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
that forms the annex for each physical format.
TPEG2 has a three-container conceptual structure: message management (ISO 21219-6), application (several
parts) and location referencing (ISO 21219-7 – this document). This structure has flexible capability and can
v
accommodate many differing use cases that have been proposed within the TTI sector and more broadly 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. Note that the list below is potentially incomplete, as it is possible that new TPEG2 parts
will be introduced after the publication of this document.
— Toolkit parts: TPEG2-INV (ISO 21219-1), TPEG2-UML (ISO 21219-2), TPEG2-UBCR (ISO 21219-3), TPEG2-
UXCR (ISO 21219-4), TPEG2-SFW (ISO 21219-5), TPEG2-MMC (ISO 21219-6), TPEG2-LRC (ISO 21219-7
– this document).
— Special applications: TPEG2-SNI (ISO 21219-9), TPEG2-CAI (ISO 21219-10), TPEG2-LTE (ISO/TS 21219-24).
1)
— Location referencing: TPEG2-OLR (ISO/TS 21219-22), TPEG2-GLR (ISO 21219-21 ), TPEG2-TLR
(ISO 17572-2), TPEG2-DLR (ISO 17572-3).
— Applications: TPEG2-PKI (ISO 21219-14), TPEG2-TEC (ISO 21219-15), TPEG2-FPI (ISO 21219-16),
TPEG2-SPI (ISO 21219-17), TPEG2-TFP (ISO 21219-18), TPEG2-WEA (ISO 21219-19), TPEG2-RMR
2)
(ISO/TS 21219-23), TPEG2-EMI (ISO 21219-25 ), TPEG2-VLI (ISO/TS 21219-26).
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 with both long-term, unchanging
content and highly dynamic content, such as parking information.
This document is based on the TISA specification technical/editorial version reference:
SP19001 _3.0_001
1) Under preparation. Stage at the time of publication: ISO/DIS 21219-21:2024.
2) Under preparation. Stage at the time of publication: ISO/PRF 21219-25:2024.
vi
International Standard ISO 21219-7:2024(en)
Intelligent transport systems — Traffic and travel information
(TTI) via transport protocol experts group, generation 2
(TPEG2) —
Part 7:
Location referencing container (TPEG2-LRC)
1 Scope
This document establishes the method of signalling the specific location referencing used by all TPEG2
applications that require detailed location information to be delivered to client devices. This document
describes the TPEG2-Location Referencing Container (TPEG2-LRC) and shows how it is used to signal which
specific location referencing method is in use for a particular TPEG message. It is able to handle location
referencing methods that are external to the ISO 21219 series and the internal location referencing methods
defined as parts of this series.
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 17572-2, Intelligent transport systems (ITS) — Location referencing for geographic databases — Part 2:
Pre-coded location references (pre-coded profile)
ISO 17572-3, Intelligent transport systems (ITS) — Location referencing for geographic databases — Part 3:
Dynamic location references (dynamic profile)
ISO 21219-1, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol experts
group, generation 2 (TPEG2) — Part 1: Introduction, numbering and versions (TPEG2-INV)
ISO 21219-9, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol experts
group, generation 2 (TPEG2) — Part 9: Service and network information (TPEG2-SNI)
ISO 21219-14, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2) — Part 14: Parking information (TPEG2-PKI)
ISO 21219-15, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2) — Part 15: Traffic event compact (TPEG2-TEC)
3)
ISO 21219-21:— , Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2) — Part 21: Geographic location referencing (TPEG-GLR)
ISO/TS 21219-22, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2) — Part 22: OpenLR location referencing (TPEG2-OLR)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3) Under preparation. Stage at the time of publication: ISO/DIS 21219-21:2024.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
TPEG client
end user's device, usually consisting of a bearer level tuner/receiver, a TPEG decoder and a human machine
interface
3.2
dynamic location reference
location reference generated on the fly based on geographic properties in a digital map database
3.3
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 plain-language manner
directly to the end-user (i.e. text, speech or icons) or to be used for navigational purposes, for example, for map-based
systems.
3.4
location referencing container
concept applied to the grouping of all the location referencing elements, of a TPEG-Message, together in one place
Note 1 to entry: Many TPEG applications are designed to deliver TPEG messages, which consist of three high level
containers, each with one or more elements. These containers are for: message management, application specific
information and location referencing information. Some special application messages do not include a location
referencing container, such as a cancellation message. Each container does not necessarily have all possible lower-
level elements included.
Note 2 to entry: Figure 1 shows the “container view” structure used, for example, when a TPEG2-TEC (ISO 21219-15)
application message is generated to describe a road event and location references need to be given to the end-user.
Figure 1 — The “container view” of a TPEG message
Note 3 to entry: The main purpose of the location referencing container is to provide both human-understandable and
machine-readable elements to appropriate client decoders. It may be delivered to a “thin client”, which for example is
only able to convey limited location referencing information to the end user or it may be delivered to a “thick client”
using a considerable number of elements and using considerable processing power to filter the information for a
comprehensive display to an end user.
3.5
message
collection of coherent information sent through the information channel describing an event, a collection of
related events, or status information, for example, and including message management information
3.6
pre-coded location reference
location reference using a unique identifier that is agreed upon in both sender and receiver systems to select
a location from a set of agreed locations
3.7
TPEG server
functionality used by the service provider to distribute or deliver the TPEG data to TPEG client devices
4 Abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO 21219-1, ISO 21219-9, ISO 21219-14,
ISO 21219-15, and the following apply.
DLR dynamic location referencing
DLR1 DLR method as defined in ISO 17572-3
ETL extended TMC location reference
NDS navigation data standard
ULR universal location referencing
VICS vehicle information and communication system – Japanese-developed real-time road traffic in-
formation system providing congestion and regulation information
5 Toolkit specific constraints
5.1 Application identification
TPEG applications are described by the TPEG specifications in the ISO 21219 series and are placed at the
highest layers of the OSI protocol stack, ISO/IEC 7498-1. Each TPEG application (e.g. TPEG2-TEC) is assigned
a unique number, called the application identity (AID). In this respect, the TPEG2-LRC is not 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.
Loading comments...