ISO 21219-17:2023

Intelligent transport systems - Traffic and travel information via transport protocol experts group, generation 2 (TPEG2) - Part 17: Speed information (TPEG2-SPI)

This document defines the TPEG Speed information (SPI) application for reporting speed information for travellers. Speed limits are usually indicated to the driver through roadside signs. Drivers who are aware of the speed limit at all times are more likely to drive safely, which improves road safety. Most speed limit signs are static and remain unchanged for years and are thus available through navigation system map databases. However, there is an increasing number of variable message signs, temporary signing (e.g. for road works) and also changed speed limits which are not yet reflected in the map databases. With the TPEG-SPI application, speed limit information is offered in an accurate way so that different lanes and different vehicle types can be differentiated. TPEG-SPI also allows the drivers to be aware of the current allowed (maximum) speed, by delivering timely information about the current position and values of speed limits to the navigation or driver assistance systems. These data are seen as informational and are intended to be encoded in a compact way to minimize bandwidth consumption. TPEG2-SPI supports direct and indirect speed limits. Direct speed limits are used for signs showing a maximum speed at which a vehicle is allowed to travel. Such speed limit signs can be static or dynamic. Indirect speed limits refer to the speed of other road users. It is primarily the vehicle in front of the own vehicle that is used as a reference.

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 17: Information de vitesse (TPEG2-SPI)

General Information

• Status: Published
• Publication Date: 24-May-2023
• ICS: 03.220.01 - Transport in general
• ICS: 03.220.20 - Road transport
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204/WG 10 - Traveller information systems
• Current Stage: 6060 - International Standard published
• Start Date: 25-May-2023
• Due Date: 06-Apr-2023
• Completion Date: 25-May-2023

Relations

• Consolidated By: ISO 15708-4:2025 - Non-destructive testing - Radiation methods for computed tomography - Part 4: Qualification
• Effective Date: 29-Jul-2023

Overview

ISO 21219-17:2023 - TPEG2-SPI (Speed information) is part of the ISO 21219 series for TPEG Generation 2 and defines the TPEG Speed Information (SPI) application used to report speed limits and speed-related data to travellers and vehicle systems. The standard specifies a compact, bandwidth-efficient encoding for delivering current speed limits - including static, variable and temporary signs - and supports differentiation by lane and vehicle type. It delivers timely speed data to navigation, driver assistance and telematics systems so drivers and automated systems can be aware of current permitted (maximum) speeds.

Key topics and technical requirements

• Scope and purpose: Reporting speed information for travellers; supporting both static and dynamic speed signage (e.g., variable message signs, temporary roadworks limits).
• Message structure: Defines SPI message components (SpeedInformationMessage, SpeedInformation, MMCSwitch, links for message management and location referencing).
• Data modelling: SPI datatypes (e.g., LaneNumber, SpeedLimitSegment) and enumerations/tables (SpeedInformationType, Context, VehicleType, InformationUnit).
• Direct vs. indirect limits:
  • Direct speed limits - explicit maximum speeds shown by signs (static or dynamic).
  • Indirect speed limits - inferred limits referencing other road users (e.g., vehicle in front).
• Location referencing: Integrates with TPEG2 location referencing options to map speed data to precise positions and lanes.
• Physical formats: Conversion rules for binary and XML (tpegML) representations are included in normative annexes to enable interoperable distribution.
• Compact encoding & bandwidth efficiency: Designed to minimize data size for broadcast and mobile networks.
• Extensibility and versioning: Application identification, version signalling and ordered components to support evolution and interoperability.

Practical applications and who uses it

• Navigation system vendors - integrate up-to-date speed limits (including temporary or dynamic changes) into route guidance and map updates.
• Automotive OEMs & ADAS developers - feed current speed limits to driver assistance systems (speed warnings, adaptive cruise control).
• Telematics & fleet operators - enforce compliance, manage speed-related alerts and improve driver safety.
• Traffic management centers & ITS service providers - broadcast dynamic speed regulations and temporary restrictions to road users.
• Map data providers - augment static map databases with live speed updates for lane- and vehicle-specific limits.

Benefits include improved road safety through timely awareness of legal speed limits, better support for dynamic traffic control, and efficient use of bandwidth for large-scale distribution.

Related standards

• ISO 21219-1 (TPEG2-INV) - introduction, numbering and versions
• ISO 21219-3 / -4 - UML-to-binary and UML-to-XML conversion rules
• ISO 21219-5 (Service framework), ISO 21219-6 (Message management container)
• Location referencing parts in the TPEG2 family (e.g., ISO/TS 21219-7 and related TLR/DLR/GLR parts)

Keywords: ISO 21219-17, TPEG2-SPI, TPEG Speed information, intelligent transport systems, speed limit information, variable message signs, navigation systems, driver assistance, compact encoding.

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 21219-17
First edition
2023-05
Intelligent transport systems — Traffic
and travel information via transport
protocol experts group, generation 2
(TPEG2) —
Part 17:
Speed information (TPEG2-SPI)
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 17: Information de vitesse (TPEG2-SPI)
Reference number
© ISO 2023
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: [phone]
Email: [e-mail]
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 . 2
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 Extensibility . 3
5.5 TPEG service component frame . 4
6 SPI structure . 4
7 SPI message components .4
7.1 SpeedInformationMessage . 4
7.2 SpeedInformation . 5
7.3 MMCSwitch . 5
7.4 MessageManagementContainerLink . 5
7.5 MMCMasterLink . 6
7.6 MMCPartLink . 6
7.7 LocationReferencingLink . 6
8 SPI datatypes .6
8.1 LaneNumber . 6
8.2 SpeedLimitSegment . 7
9 SPI tables .8
9.1 spi001:SpeedInformationType . 8
9.2 spi002:Context . 9
9.3 spi003:VehicleType . . 10
9.4 spi004:InformationUnit . 11
Annex A (normative) TPEG application, TPEG-binary representation .13
Annex B (normative) TPEG application, tpegML representation.18
Annex C (informative) Speed limit road signs (examples) .24
Annex D (informative) Modelling examples .25
Bibliography .35
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 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 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.
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, later 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, later 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, later 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 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).
TPEG2 is embodied in the ISO 21219 series and it comprises many parts that cover an 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, to minimize drafting errors; this file forms the annex for each
physical format.
v
TPEG2 has a three-container conceptual structure: message management (ISO 21219-6), application
(several 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. Note that the list below is potentially incomplete, as there is the possibility 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/TS 21219-7).
— Special applications: TPEG2-SNI (ISO 21219-9), TPEG2-CAI (ISO 21219-10), TPEG2-LTE
(ISO/TS 21219-24).
— Location referencing: TPEG2-OLR (ISO/TS 21219-22), TPEG2-GLR (ISO/TS 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 - this document), TPEG2-TFP (ISO 21219-18), TPEG2-WEA (ISO 21219-19),
TPEG2-RMR (ISO/TS 21219-23), TPEG2-EMI (ISO/TS 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:
SP19005/1.0/001.
vi
INTERNATIONAL STANDARD ISO 21219-17:2023(E)
Intelligent transport systems — Traffic and travel
information via transport protocol experts group,
generation 2 (TPEG2) —
Part 17:
Speed information (TPEG2-SPI)
1 Scope
This document defines the TPEG Speed information (SPI) application for reporting speed information
for travellers. Speed limits are usually indicated to the driver through roadside signs. Drivers who are
aware of the speed limit at all times are more likely to drive safely, which improves road safety. Most
speed limit signs are static and remain unchanged for years and are thus available through navigation
system map databases. However, there is an increasing number of variable message signs, temporary
signing (e.g. for road works) and also changed speed limits which are not yet reflected in the map
databases.
With the TPEG-SPI application, speed limit information is offered in an accurate way so that different
lanes and different vehicle types can be differentiated. TPEG-SPI also allows the drivers to be aware
of the current allowed (maximum) speed, by delivering timely information about the current position
and values of speed limits to the navigation or driver assistance systems. These data are seen as
informational and are intended to be encoded in a compact way to minimize bandwidth consumption.
TPEG2-SPI supports direct and indirect speed limits. Direct speed limits are used for signs showing a
maximum speed at which a vehicle is allowed to travel. Such speed limit signs can be static or dynamic.
Indirect speed limits refer to the speed of other road users. It is primarily the vehicle in front of the own
vehicle that is used as a reference.
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 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-3, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2) — Part 3: UML to binary conversion rules (TPEG2-UBCR)
ISO 21219-4, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2) — Part 4: UML to XML conversion rules
ISO 21219-5, Intelligent transport systems — Traffic and travel information (TTI) via transport protocol
experts group, generation 2 (TPEG2) — Part 5: Service framework (TPEG2-SFW)
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-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 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
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
speed limit
maximum (or, in some cases, minimum) speed at which road vehicles may legally travel on particular
stretches of road
4 Abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO 21219-1, ISO 21219-9,

ISO 21219-15 and the following apply.
ADC application data container
AID application identification
CEN Comité Européen de Normalisation
EBU European Broadcasting Union
ISO International Organization for Standardization
ITS intelligent transport systems
LRC location referencing container
MMC message management container
OSI open systems interconnection
SID TPEG service ID
SFW TPEG service framework
SNI service and network information
TISA traveller information services association
TPEG transport protocol expert group
TMC traffic message channel
TTI traffic and traveller information
UML unified modelling language
XML extensible markup language
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 identity (AID). An AID number is defined in ISO 21219-1 whenever a new
application is developed.
The AID number is used within the TPEG2-SNI application (ISO 21219-9) to indicate how to process
TPEG content. It 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 can have an impact on client devices.
The version numbering principle is defined in ISO 21219-1.
Table 1 shows the current version numbers for signalling SPI within the SNI application.
Table 1 — Current version numbers for signalling of SPI
major version number 1
minor version number 1
5.3 Ordered components
TPEG2-SPI requires a fixed order of TPEG components. The order for the SPI message component
is shown in Figure 1. The first component shall be the MMC. 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
ADC component(s) which includes the application-specific information.
Figure 1 — Composition of TPEG messages
5.4 Extensibility
The requirement of a fixed component order does not affect the extension of TPEG2-SPI. Future
application extensions may insert new components or may replace existing components by new
ones without losing backward compatibility, i.e. a TPEG2-SPI decoder shall be able to detect and skip
unknown components.
5.5 TPEG service component frame
TPEG2-SPI shall use the "service component frame with dataCRC and messageCount" conforming to
ISO 21219-5.
6 SPI structure
The structure of SPI messages is shown in Figure 2. Annex A and Annex B specify respectively the
binary format and XML format of the TPEG2-SPI application for use in transmission.
Annex C provides examples for speed limit signs and Annex D provides modelling examples for the SPI
application.
Figure 2 — SPI message structure
7 SPI message components
7.1 SpeedInformationMessage
A SpeedInformationMessage includes the message management container with management
information related to the overall message. To transfer the actual payload, a simple speed information
data container is provided. This container includes all speed information related to a location which is
provided in a dedicated location referencing container.
Table 2 defines the SpeedInformationMessage component.
Table 2 — SpeedInformationMessage
Name Type Multiplic- Description
ity
Ordered components
mmt MMCSwitch 1 Message management container.
speedInfo SpeedInformation 0.1 Describes the speed information.
location LocationReferencingLink 0.1 Location referencing container (always included
except for cancellation of a message and partial
updates).
7.2 SpeedInformation
The speed information component provides information on the speed information type and additional
attributes. It contains more detailed information about the limit itself and the affected parts of the
location.
Speed limits can have start and stop time. Context and information about the source of the information
may be provided on the background of the speed limit information.
Table 3 defines the SpeedInformation component.
Table 3 — SpeedInformation
Name Type Multiplic- Description
ity
spiType spi001: SpeedInformationType 1 The speed information type shall provide
information on the general sort of a speed
limit message.
speedLimitSegment SpeedLimitSegment 1.* SpeedLimitSegments should be ordered with
an increasing speedLimitStartOffset and in
case of the same start offset the order should
consider increased lane numbers.
informationUnit s pi 0 0 4 : I n f or m a t ionUn i t 0.1 The information unit provides the unit in
which the speed limit information provided
in this message is dimensioned.
The information unit may be omitted for the
end of a speed limit.
startTime DateTime 0.1 n.a.
stopTime DateTime 0.1 n.a.
source ShortString 0.* Information about the source of this speed
limit. The source may be a “C-ITS authority
[3]
data set” (see ISO/TS 17426).
context spi002: Context 0.1 The context can provide additional infor-
mation to the driver for understanding the
reason for this restriction.
7.3 MMCSwitch
The MMCSwitch component is a placeholder for the MessageManagementContainerLink,
MMCMasterLink and MMCPartLink.
7.4 MessageManagementContainerLink
The MMCLink component is used only if all information of a SpeedInformationMessage is transmitted
within one complete message.
7.5 MMCMasterLink
The MMCMasterLink component is used in combination with MMCPartLink components to link static
and dynamic parts of a message that are transmitted independently.
7.6 MMCPartLink
MMCPartLink components are used in combination with an MMCMasterLink component to link static
and dynamic parts of a message that are transmitted independently.
7.7 LocationReferencingLink
The LocationReferenceLink component is a placeholder for the LocationReferencingContainer (LRC).
It assigns the SPI application a specific local component ID for the LRC container. All component IDs
within the LRC container are local to the LRC toolkit.
The component contains all information describing the location where the speed limit values are
valid. It specifies a starting point and a route to which the SpeedInformation refers by giving offsets to
indicate the exact position of a speed limit gantry along such a route.
It is allowed to use a flag indicating that both sides of the route are affected (both directions) in case
the LRM supports it and the speed information provided in the ADC is identical for both directions. An
example of how such a case can be encoded is provided in the modelling examples in Annex D.
8 SPI datatypes
8.1 LaneNumber
Lane numbering is a way to address each lane of a road stretch individually. It assigns each lane a
unique number until the physical road layout changes. A physical road layout changes in cases where
new lanes start or existing lanes end.
The lane numbering schema should follow these rules.
a) Lanes are numbered from the curb to the middle of the road. Right-hand traffic lanes are therefore
numbered from the right to the left relating to the driving direction. Left-hand traffic lanes are
numbered from left to right relating to the driving direction.
b) The lowest possible number is 0 and only consecutive integer numbers are used.
c) The hard shoulder is always number 0:
1) this is the leftmost lane in case of left-hand driving (if exists);
2) this is the rightmost lane in case of right-hand driving (if exists);
3) additional hard shoulders are numbered consecutively (also applicable for hard shoulders next
to the divider).
d) The first drivable lane for vehicles is number 1. This is applicable in case of no hard shoulder or just
one hard shoulder.
e) All lanes which are physically available, count.
f) Lanes which are temporarily closed or opened keep their original number.
g) If the physical layout changes then the location shall be split.
h) Lane numbers are per driving direction.
i) In case of overlapping lanes (3 lanes with the middle lane drivable from both directions, or a single
physical lane drivable from both directions) the lane which is drivable from both directions counts
from both directions.
Table 4 defines the LaneNumber datatype.
Table 4 — LaneNumber
Name Type Multiplic- Description
ity
a
hardShoulder Boolean 1 true, if the hard shoulder exists and is selected .
lane1 Boolean 1 true, if the lane is selected.
lane2 Boolean 1 true, if the lane is selected.
lane3 Boolean 1 true, if the lane is selected.
lane4 Boolean 1 true, if the lane is selected.
lane5 Boolean 1 true, if the lane is selected.
lane6 Boolean 1 true, if the lane is selected.
lane7 Boolean 1 true, if the lane is selected.
lane8 Boolean 1 true, if the lane is selected.
lane9 Boolean 1 true, if the lane is selected.
lane10 Boolean 1 true, if the lane is selected.
lane11 Boolean 1 true, if the lane is selected.
lane12 Boolean 1 true, if the lane is selected.
lane13 Boolean 1 true, if the lane is selected.
lane14 Boolean 1 true, if the lane is selected.
lane15 Boolean 1 true, if the lane is selected.
lane16 Boolean 1 true, if the lane is selected.
lane17 Boolean 1 true, if the lane is selected.
lane18 Boolean 1 true, if the lane is selected.
lane19andMore Boolean 1 true, if the lane and potential further lanes are select-
ed.
b c
innerSideHardShoulder Boolean 1 true, if a Central Reserve exists and is selected .
a
hardShoulder is usually only driveable in special cases.
b
Terms equivalent for Central Reserve UK are Median Strip and Median Divider in the US.
c
innerHardShoulder is usually only driveable in special cases.
8.2 SpeedLimitSegment
A SpeedLimitSegment contains the speed limit information for a segment starting at the position
defined by an offset from a starting point defined by the LRC.
If segments are not consecutive, then such gaps shall be seen as information "unknown". A service
provider can potentially not have a full coverage of speed information but can still send multiple
segments in one message. Gaps can also occur at the start or at the end of a location.
Table 5 defines the SpeedLimitSegment datatype.
Table 5 — SpeedLimitSegment
Name Type Multiplic- Description
ity
speedLimitValue IntUnTi 0.1 The speed limit value. The unit can be
found in the enclosing component.
If no value is given, the default value
should be “no limit” or “end of speed
limit”.
A speed limit value is valid until a
segment with the next higher offset and
same lane replaces it or the end of the
segment or the end of the location is
reached.
speedLimitValueWet IntUnTi 0.1 Speed limit value to be used in wet
conditions. The unit can be found in the
enclosing component.
spiType spi001: SpeedInformationType 0.1 The speed information type shall pro-
vide information on the general sort of a
speed limit message. If given, the value
overrides the attribute in the SpeedIn-
formation for this segment.
informationUnit s pi 0 0 4 : I n f or m a t ionUn i t 0.1 The information unit provides the unit
in which the speed limit information
provided in this segment is dimensioned.
If given, the value overrides the attrib-
ute in the SpeedInformation for this
segment.
speedLimitStartPosi- IntUnLoMB 0.1 Offset (in m) following the stretch from
tion the starting point defined in the LRC.
If no value is given, then the start of the
location should be used. This equals
speedLimitStartPosition=0.
speedLimitLength IntUnLoMB 0.1 Indicates the length (in m) for which the
actual speed limit is applied.
If no value is given, then the length of the
segment is determined by the start of the
next segment in order or at the end of the
location.
vehicleTypeRestriction spi003: VehicleType 0.* The vehicle type should be used in cases
where the speed limit is only applicable
for certain types of vehicle and not all.
If no value is given, then the restriction
is applicable to all vehicle types.
affectedLanes LaneNumber 0.1 The affected lanes provide information
on which lanes the actual speed limit is
applicable in.
If no value is given, then all lanes are
affected.
9 SPI tables
9.1 spi001: SpeedInformationType
The speed information type provides information on the general type of a speed limit message.
Table 6 enumerates the possible values for type spi001: SpeedInformationType.
Table 6 — spi001: SpeedInformationType
Code Reference-English Comment Example
'word'
0 unknown
static maximum speed
limit
Variable maximum speed limit is appli-
variable maximum
2 cable where variable speed limits are
speed limit
displayed.
Temporary maximum speed limit is
temporary maximum
3 applicable only in given circumstances
speed limit
such as weather, roadworks, etc.
general speed infor-
mation
end of maximum
speed limit
minimum allowed
speed
end of minimum al-
lowed speed
Recommended speeds are proposed by
(any) parties. Use cases can be adjust-
8 recommended speed ment of the vehicle speed optimally for
traffic flow efficiency or safety of the
upstream traffic state.
end of recommended
speed
Advisory speed limits may provide a
safe suggested speed in an area or warn
of the safe maximum speed for danger-
10 advisory speed limit
ous curves. Advisory speed limits are
non-binding speed limits, recommend-
ed by (official) road authorities.
end of advisory speed
limit
minimum allowed dis-
12 tance to predecessor
vehicle
recommended dis-
13 tance to predecessor
vehicle
255 undefined
9.2 spi002: Context
The context optionally provides additional information about the reason of a restriction. Context can be
used, for example, for driver information.
Table 7 enumerates the possible values for type spi002: Context.
Table 7 — spi002: Context
Code Reference-English Comment Example
'word'
0 unknown
1 traffic
2 accident
3 weather
4 visibility
5 roadworks
6 shockwave damping
This type describes all kind of environ-
environment protec-
7 ment protections including air protec-
tion
tion and noise protection.
8 merging lanes
9 school
Examples are children, elderly people,
10 vulnerable road users
people with a disability.
This type includes use cases like bad
dangerous road con-
11 road, damaged road, trees near the road
ditions
and others.
Road stretch with synchronized traffic
signals where it is possible to drive
12 green wave
through all green lights when driving at
a specified speed.
13 road safety
14 regulatory message
255 undefined
9.3 spi003: VehicleType
The vehicle type should be used in cases where the speed limit is only applicable for certain types of
vehicle and not all. If not provided, the speed limit affects all type of vehicles.
Table 8 enumerates the possible values for type spi003: VehicleType.
Table 8 — spi003: VehicleType
Code Reference-English Comment Example
'word'
0 unknown
In accordance with the definition in
1 passenger car
ISO 3833.
In accordance with the definition in
2 bus
ISO 3833.
In accordance with the definition in
ISO 3833.
3 commercial vehicle
NOTE This is also called a "goods vehicle".
TTabablele 8 8 ((ccoonnttiinnueuedd))
Code Reference-English Comment Example
'word'
Based on the definition of commercial
vehicle in ISO 3833, except that their mass
given in tonnes is limited between 3,5 and 7
light commercial
tonnes depending on national/local regula-
vehicle
tion and/or professional specifications.
NOTE This is also called a "van" or "light
goods vehicle".
Based on the definition of commercial vehi-
cles in ISO 3833, except that their mass given
in tonnes is over the limit (ranging from 3,5
5 heavy goods vehicle
to 7 tonnes) of light commercial vehicles.
They include tractor vehicles designed for
towing semi-trailers.
In accordance with the definition in
6 moped
ISO 3833.
In accordance with the definition in
7 motorcycle
ISO 3833.
Combination of motor vehicles and towed
8 vehicle with trailer vehicles in accordance with the definition in
ISO 3833.
Combination of passenger car and cara-
9 vehicle with caravan van in accordance with the definition in
ISO 3833.
Special category of commercial vehicles and
high sided motor buses as defined by ISO 3833 that are tall in
vehicle relation with their width (such as a lorry or
a double-decker bus).
255 undefined
9.4 spi004: InformationUnit
The information unit provides the unit in which the speed limit information provided in this message is
dimensioned.
Table 9 enumerates the possible values for type spi004: InformationUnit.
Table 9 — spi004: InformationUnit
Code Reference-English Comment Example
'word'
0 unknown
1 kilometresPerHour
2 milesPerHour
NOTE Usage deprecated in favour of
3 metresPerSecond
centimetresPerSecond.
May be used with the speed infor-
mation types used with 'minimum
4 metres allowed distance to predecessor
vehicle' and 'recommended distance to
predecessor vehicle'.
TTaabblle 9 e 9 ((ccoonnttiinnueuedd))
Code Reference-English Comment Example
'word'
The unit tenth of a second ensures that
values like 1,5s can be sent using an in-
teger number. The example 1,5s needs
to be encoded as "15 tenth of a second"
5 tenth of a second
May be used with the speed infor-
mation types used with 'minimum
allowed distance to predecessor
vehicle' and 'recommended distance to
predecessor vehicle
Chevrons are markings on the road
(e.g. in the UK).
May be used with the speed infor-
6 chevrons
mation types used with 'minimum
allowed distance to predecessor
vehicle' and 'recommended distance to
predecessor vehicle'.
May be used with the speed infor-
mation types used with 'minimum
7 centimetresPerSecond allowed distance to predecessor
vehicle' and 'recommended distance to
predecessor vehicle'.
255 undefined
Annex A
(normative)
TPEG application, TPEG-binary representation
A.1 Introduction
This annex provides the TPEG-Binary representation that shall follow the UML to binary conversion
rules specified in ISO 21219-3.
A.2 Message components
A.3 List of generic component IDs
Table A.1 shows a list of generic component IDs.
Table A.1 — Generic component IDs
Name ID
SpeedInformationMessage 0
MessageManagementContainerLink 1
MMCMasterLink 2
MMCPartLink 3
LocationReferencingLink 4
SpeedInformation 5
A.4 SpeedInformationMessage
:=
(0), id of this component.
(lengthComp), number of bytes in component, excluding the ID and length-
Comp indicator.
(lengthAttr), number of bytes in attributes.
ordered {
(mmt), Message management container.
n *(speedInfo)[0.1], Describes the speed information.
N *(location) Location referencing container (always included except for
[0.1] cancellation of a message and partial updates).
};
A.5 SpeedInformation.
:=
(5), id of this component.
(lengthComp), number of bytes in component, excluding the id and
lengthComp indicator.
(lengthAttr), number of bytes in attributes.
(spiType), The speed information type shall provide information on
the general sort of a speed limit message.
(n),
n *(speedLimitSeg- SpeedLimitSegments should be ordered with an increas-
ment), ing speedLimitStartOffset and in case of the same start
offset the order should consider increased lane numbers.
BitArray(selector),
If (bit 0 of selector is set)
(InformationUnit), The information unit provides the unit in which the
speed limit information provided in this message is
dimensioned.
The information unit may be omitted for the end of a
speed limit.
If (bit 1 of selector is set)
(startTime),
If (bit 2 of selector is set)
(stopTime),
If (bit 3 of selector is set)
{
(n),
n *(source), Information about the source of this speed limit. The source
may be a “C-ITS authority data set” (see ISO/TS 17426).
}
If (bit 4 of selector is set)
(context); The context should provide additional information to the
driver to understand the speed limit.
A.6 MMCSwitch
:=
(x), id of this component.
(lengthComp), number of bytes in component, excluding the id and lengthComp indicator.
(lengthAttr); number of bytes in attributes.
A.7 MessageManagementContainerLink
>:=
External; see MessageManagementContainer specification.
A.8 MMCMasterLink
>:=
External; see MMCMasterMessage specification.
A.9 MMCPartLink
>:=
External; see MMCMessagePart specification.
A.10 LocationReferencingLink
:=
External; see LocationReferencingContainer specification.
A.11 SPI Datatypes
A.12 LaneNumber
:=
BitArray(selector),
if (bit 0 of selector is set)
(hardShoulder), true, if the hard shoulder exists and is selected.
if (bit 1 of selector is set)
(lane1), true, if the lane is selected.
if (bit 2 of selector is set)
(lane2), true, if the lane is selected.
if (bit 3 of selector is set)
(lane3), true, if the lane is selected.
if (bit 4 of selector is set)
(lane4), true, if the lane is selected.
if (bit 5 of selector is set)
(lane5), true, if the lane is selected.
if (bit 6 of selector is set)
(lane6), true, if the lane is selected.
if (bit 7 of selector is set)
(lane7), true, if the lane is selected.
if (bit 8 of selector is set)
(lane8), true, if the lane is selected.
if (bit 9 of selector is set)
(lane9), true, if the lane is selected.
if (bit 10 of selector is set)
(lane10), true, if the lane is selected.
if (bit 11 of selector is set)
(lane11), true, if the lane is selected.
if (bit 12 of selector is set)
(lane12), true, if the lane is selected.
if (bit 13 of selector is set)
(lane13), true, if the lane is selected.
if (bit 14 of selector is set)
(lane14), true, if the lane is selected.
if (bit 15 of selector is set)
(lane15), true, if the
...