ISO/TS 19321:2020

TECHNICAL ISO/TS
SPECIFICATION 19321
Second edition
2020-09
Intelligent transport systems —
Cooperative ITS — Dictionary of
in-vehicle information (IVI) data
structures
Systèmes intelligents de transport — Coopérative STI — Dictionnaire
de structures de données d'informations dans les véhicules (IVI)
Reference number
©
ISO 2020
© ISO 2020
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 © ISO 2020 – All rights reserved

Contents Page
Foreword .v
Introduction .vii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 3
5 In-vehicle information data structure . 4
5.1 Structural model . 4
5.1.1 General model . 4
5.1.2 Conceptual zones . 5
5.2 Location referencing . 7
5.2.1 General. 7
5.2.2 Geographic positioning . 7
5.2.3 Map-based location referencing . 8
6 IVI Containers . 8
6.1 IVI Management Container . 8
6.1.1 Definition . 8
6.1.2 Usage — IVI Management Container . 9
6.2 IVI Location Containers .10
6.2.1 General.10
6.2.2 Geographic Location Container (GLC) . .11
6.2.3 Map Location Container (MLC) .12
6.3 IVI Application Containers .13
6.3.1 General.13
6.3.2 General IVI Container .13
6.3.3 Road Configuration Container.15
6.3.4 Text Container .16
6.3.5 Layout Container .18
6.3.6 Automated Vehicle Container .19
6.3.7 Road Surface Container .20
7 Description of data frames and data elements .21
7.1 General .21
7.2 Data Frames .21
7.2.1 AbsolutePosition .21
7.2.2 AbsolutePositionWAltitude .21
7.2.3 AnyCatalogue .21
7.2.4 AutomatedVehicleRule.22
7.2.5 CompleteVehicleCharacteristics .22
7.2.6 ComputedSegment .23
7.2.7 DeltaPosition .23
7.2.8 ISO14823Attribute .23
7.2.9 ISO14823Code .23
7.2.10 LaneInformation .24
7.2.11 LaneCharacteristics .24
7.2.12 LayoutComponent .25
7.2.13 LoadType .25
7.2.14 MapReference .25
7.2.15 PlatooningRule .25
7.2.16 PolygonalLine .26
7.2.17 RoadSurfaceDynamicCharacteristics .27
7.2.18 RoadSurfaceStaticCharacteristics .27
7.2.19 RSCode .27
7.2.20 Segment .27
7.2.21 Text .28
7.2.22 TractorCharacteristics.28
7.2.23 TrailerCharacteristics .28
7.2.24 TrainCharacteristics .28
7.2.25 VcCode .28
7.2.26 VehicleCharacteristicsFixValues .29
7.2.27 VehicleCharacteristicsRanges .29
7.2.28 Zone . .30
7.2.29 Data frames which are lists .30
7.3 Data Elements .31
7.3.1 BankingAngle .31
7.3.2 ComparisonOperator .31
7.3.3 Condition .31
7.3.4 DefinitionAccuracy . .32
7.3.5 Depth .32
7.3.6 Direction.32
7.3.7 DriverCharacteristics .32
7.3.8 FrictionCoefficient .33
7.3.9 GapBetweenVehicles .33
7.3.10 GoodsType .33
7.3.11 IviIdentificationNumber .33
7.3.12 IviLaneWidth.33
7.3.13 IviPurpose.34
7.3.14 IviStatus .34
7.3.15 IviType .34
7.3.16 LaneDelimitation .34
7.3.17 LaneId .35
7.3.18 LaneMarkingStatus .35
7.3.19 LaneStatus .35
7.3.20 LaneType .35
7.3.21 MarkingColour .36
7.3.22 MaterialType .37
7.3.23 MaxLenghtOfPlatoon .37
7.3.24 MaxNoOfVehicles .37
7.3.25 PriorityLevel .37
7.3.26 Provider .37
7.3.27 RSCUnit .37
7.3.28 SaeAutomationLevel .38
7.3.29 Temperature .38
7.3.30 TreatmentType .38
7.3.31 VcClass .38
7.3.32 VcOption .38
7.3.33 WearLevel .39
7.3.34 Zid .39
Annex A (normative) ASN.1 modules .40
Annex B (informative) Visual examples of location container .41
Bibliography .48
iv © ISO 2020 – All rights reserved

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
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 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 the following
URL: www .iso .org/ iso/ foreword .html.
This document was prepared by the European Committee for Standardization (CEN) Technical
Committee CEN/TC 278, Intelligent transport systems (ITS), in collaboration with Technical Committee
ISO/TC 204, Intelligent transport systems, in accordance with the Agreement on technical cooperation
between ISO and CEN (Vienna Agreement).
This second edition cancels and replaces the first edition (ISO/TS 19321:2015) which has been
technically revised.
The main changes compared to the previous edition are as follows.
— The Scope has been edited.
— Several containers have been renamed or newly introduced and an "Automated Vehicle Container"
has been added to better manage automated vehicles.
— The abstract syntax notation one (ASN.1) code in Annex A has been captured separately. This edition
is backwards compatible with the previous edition in that it adds information elements (e.g. data
elements and data frames) to the IVI Structure by using ASN.1 extensions. The ASN.1 extension
feature ensures that implementations of the previous edition can correctly parse IVI Structures
compliant with this edition and process the information specified in the previous edition without
needing knowledge about the extensions.
— The former Annex B has been replaced with new visual examples.
— C-Roads and Eco-AT documents have been added to the Bibliography.
— Data types are imported from ISO 14823 which are backwards compatible with the first edition of
this document.
— Data types are imported from updated editions of ISO 14906, ISO 17419 and ETSI/TS 102 894-2,
which are backwards compatible with the first edition of this document.
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.
vi © ISO 2020 – All rights reserved

Introduction
In a Cooperative Intelligent Transport System (C-ITS), presenting information related to the traffic
situation or regulation of a road to the driver of a vehicle is an important component of road operations.
The road operators are responsible for road setup, operation, signage, and maintenance for traffic
management and road safety, and in some countries, also for the enforcement of road laws. For road
operators, efficient transport of vehicles on roadways ensures a safe and predictable trip for all road
users. Road operators, together with equipment manufacturers, whether of vehicles or of roadside
equipment, contribute to how road information is properly presented to drivers.
So far, one defined C-ITS method for notifying road users of road and/or traffic situations and events
is by transmission of messages such as Cooperative Awareness Messages (CAM), Decentralized
Environment Notification Messages (DENM), or Basic Safety Messages (BSM).
This document supports mandatory and advisory road signage such as contextual speeds and road
works warnings. In-vehicle information can be sent by an ITS Station (ITS-S) and either corresponds to
physical road signs such as static or variable road signs or does not correspond to physical road signs (a
virtual sign) or corresponds to road works. In-vehicle information (IVI) does not include identification
of road events as already provided by DENM.
This document provides a toolbox of information elements for IVI. It can be used to fulfil the
requirements of the service provider considering the needs of receiving ITS-S. The container concept
provides a way for an ITS-S to manage the relevant IVI information, determine where the IVI is relevant,
and to provide details for the application of IVI. The description of data elements encompasses the data
syntax and semantics, i.e. a definition of data format and content, together with a description of how to
use those data elements.
This document is of an enabling nature. It does not specify which information is necessary for a certain
service, but it supports those IVI information elements that can be necessary to be transmitted to a
receiving ITS-S to carry out a certain service. Usage of the IVI information elements depends on the
specific context and application of IVI for a specific service and usage is established as mandatory or
optional only for messaging purposes, not for application purposes. The IVI Structure is intended to be
profiled to fulfil the requirements of a specific service.
This document refers to ISO 14823 as one system of standardized codes for existing road signs codes.
NOTE ISO 14823 does not contain codes for specific national or regional signs that are not commonly used,
and it does not represent a catalogue of road sign pictograms for all applicable nations.
TECHNICAL SPECIFICATION ISO/TS 19321:2020(E)
Intelligent transport systems — Cooperative ITS —
Dictionary of in-vehicle information (IVI) data structures
1 Scope
This document specifies the in-vehicle information (IVI) data structures that are required by different
intelligent transport system (ITS) services for exchanging information between ITS Stations (ITS-S).
A general, extensible data structure is specified, which is split into structures called containers to
accommodate current-day information. Transmitted information includes IVI such as contextual
speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, location-
based services, re-routing. The information in the containers is organized in sub-structures called data
frames and data elements, which are described in terms of its content and its syntax.
The data structures are specified as communications agnostic. This document does not provide the
communication protocols. This document provides scenarios for usage of the data structure, e.g. in case
of real time, short-range communications.
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 639-1:2002, Codes for the representation of names of languages — Part 1: Alpha-2 code
ISO 14823:2017, Intelligent transport systems — Graphic data dictionary
ISO 14906:2018, Electronic fee collection — Application interface definition for dedicated short-range
communication
ISO/TS 19091:2019, Intelligent transport systems — Cooperative ITS — Using V2I and I2V communications
for applications related to signalized intersections
ISO 24534-3:2016, Intelligent transport systems — Automatic vehicle and equipment identification —
Electronic registration identification (ERI) for vehicles — Part 3: Vehicle data
ETSI/TS 102 894-2 V1.3.1 (2018-08), Intelligent Transport Systems (ITS); Users and applications
requirements; Part 2: Applications and facilities layer common data dictionary
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
3.1
application data unit
data unit exchanged between ITS Station applications
3.2
container
group of data frames (3.4) and data elements (3.3) semantically belonging together in one place in the
in-vehicle information (3.8) structure
3.3
data element
DE
data type that contains one single data
[SOURCE: ETSI/TS 102 894-2 V1.3.1]
3.4
data frame
data type that contains more than one data element (3.3) in a predefined order
[SOURCE: ETSI/TS 102 894-2 V1.3.1]
3.5
detection zone
part of the road network that is passed by a vehicle in approach of the relevance zone (3.17)
3.6
digital map database
structured set of digital and alphanumeric data portraying geographic locations and relationships of
spatial features
[SOURCE: ISO 17572-1:2015, 2.1.10, modified — Note to entry has been deleted.]
3.7
driver awareness zone
parts of the road network on which a message is presented to inform drivers about upcoming situations
3.8
in-vehicle information
information contained in the in-vehicle information data structure that is required by different
intelligent transport system services
3.9
in-vehicle signage
intelligent transport system service that provides static, as well as dynamic, road sign and message
sign information to drivers
3.10
intersection
crossing and/or connection of two or more roads (3.14)
[SOURCE: ISO 17572-1:2015, 2.1.17, modified — Notes to entry have been deleted.]
3.11
link
direct topological connection between two nodes that has a unique link ID (3.12) in a given digital map
database (3.6)
[SOURCE: ISO 17572-1:2015, 2.1.20, modified — Second term “edge” and Note to entry have been
deleted.]
2 © ISO 2020 – All rights reserved

3.12
link identifier
link ID
identifier that is uniquely assigned to a link (3.11)
[SOURCE: ISO 17572-1:2015, 2.1.21, modified — Note to entry has been deleted.]
3.13
minimum dissemination area
parts of the road network where the in-vehicle signage message can be received by the potentially
targeted vehicles
3.14
road
part of the road network which is generally considered as a whole and which can be addressed by a
single identification like a road name or road number throughout
[SOURCE: ISO 17572-1:2015, 2.1.39, modified — Notes to entry have been deleted.]
3.15
road section
road segment (3.16) that is bounded by two intersections (3.10) and has the same attributes throughout
[SOURCE: ISO 17572-1:2015, 2.1.42, modified — Note to entry has been deleted.]
3.16
road segment
part of a road (3.14), having its start and end along that road
[SOURCE: ISO 17572-1:2015, 2.1.43, modified — Note to entry has been deleted.]
3.17
relevance zone
parts of the road network for which the information in an Application Container is valid
3.18
road works warning
alerts for routing road users around road construction and/or road repair
3.19
variable message sign
electronic sign board presenting text, symbols, or a combination of them
4 Abbreviated terms
ASN.1 Abstract Syntax Notation One
C-ITS Cooperative Intelligent Transport System
DE Data Element
DENM Decentralized Environmental Notification Message
DF Data Frame
GLC Geographic Location Container
ID Identification
ITS Intelligent Transport Systems
ITS-S ITS Station
IVI In-Vehicle Information
IVS In-Vehicle Signage
MAP Map Data Message
MLC Map Location Container
RWW Road Works Warning
5 In-vehicle information data structure
5.1 Structural model
5.1.1 General model
The in-vehicle information (IVI) structure represents the Application Data Unit to be transmitted and
received by an ITS Station (ITS-S). The IVI Structure shall comply with the syntax defined in Annex A
as the data type IviStructure. This means that it shall be composed of Containers defined in this
document and follow the form depicted in Figure 1.
Figure 1 — IVI Structure
The IVI Structure is extensible and other containers can be added in the future.
The IVI Structure is intended to be encapsulated in a message with the appropriate ITS Common Header,
for example, the ItsPduHeader of ETSI/TS 102 894-2. The header structure and contents are out of the
scope of this document and are for example specified in ETSI/TS 103 301.
The IVI Structure shall contain a Management Container. The information in the IVI Management
Container is applicable to the entire IVI Structure. This Container is mandatory to be present and
provides a receiving ITS-S with enough information to handle the IVI Structure and decide on its
further processing.
The IVI Structure can contain one or more Location Container(s). The Location Container describes
the essential information for applications in the receiving ITS-S. Applications can use the location
information to understand how to apply information provided by IVI Application Containers. Location
Containers can carry information relevant for different IVI Application Containers or carry the
same content but expressed in different forms (see 5.2). This enables a receiving ITS-S to choose the
appropriate location referencing system that the ITS-S supports.
The IVI Structure can contain one or more IVI Application Container(s). The IVI Application Container
provides IVI information for use by an application. Application information is self-contained and refers
to the location information for its spatial validity. Application information of the same type shall not
4 © ISO 2020 – All rights reserved

refer to overlapping Reference Zones. Each Application Container refers to zones defined in the Location
Container identified by their identifications (IDs) for the following usage:
a) Detection Zone,
b) Relevance Zone, and
c) Driver Awareness Zone.
An Application Container may optionally provide information about the minimum awareness time, that
is, the minimum time that the IVI should be available before the vehicle enters the Relevance Zone. This
MinimumAwarenessTime information can be used by the receiving ITS-S to determine the appropriate
Driver Awareness Zone.
5.1.2 Conceptual zones
When an ITS-S receives the IVI Structure, the ITS-S can interpret the application information in the
context of the appropriate location information. Principally, there are four conceptual zones:
a) Minimum Dissemination Area;
b) Detection Zone;
c) Driver Awareness Zone;
d) Relevance Zone.
The Minimum Dissemination Area refers to the minimum area where the IVI Structure is disseminated
by an ITS-S based on application requirements. The Minimum Dissemination Area is defined in the
relevant application standards or specification(s) and is therefore out of scope of this document.
In some situations, a vehicle ITS-S needs to be able to detect whether or not it is approaching a Relevance
Zone at a certain minimum time before it enters the Relevance Zone. This is, for example, to guarantee
that the Relevance Zone is detected immediately at its entry (e.g. in case of a very small Relevance Zone)
or to guarantee that the Relevance Zone is correctly detected (in case it is near to other road segments,
e.g. parallel or on different altitude level). Therefore, a Detection Zone occurs in approach to a Relevance
Zone. If a receiving ITS-S moves through the Detection Zone, then the received IVI will be enabled for
further usage in the receiving ITS-S.
The IVI can be used to inform drivers about upcoming situations in the Driver Awareness Zone. The
Driver Awareness Zone can be determined by the receiving ITS-S because the Driver Awareness Zone
can be based on the dynamic status of the receiving ITS-S and can depend on the presence of other
higher priority information to be presented. Alternatively, the Driver Awareness Zone can be provided
by the sending ITS-S for usage by the receiving ITS-S.
The Relevance Zone covers the area where the IVI is applicable.
Examples of the Detection and Relevance Zones for the spatial validity of the IVI Structure are
illustrated in Figure 2. In traffic direction East (right-hand traffic), the figure shows a Detection
Zone and a Relevance Zone for the entire carriageway. The Driver Awareness Zone can be physically
overlapping with the Detection Zone (but is not necessarily equal in size). In traffic direction West, the
figure shows lane specific Detection and Relevance Zones.
Figure 2 — Spatial validity for IVI: Detection and Relevance Zones
The Location Container always contains a definition of one or more zones which can represent a
Detection Zone, a Relevance Zone, or both. In Figure 2 in traffic direction East, from left to right, the
first zone represents a Detection Zone and the second zone represents a Relevance Zone.
In Figure 3 in traffic direction East, from left to right, the first zone represents a Detection Zone. The
second zone then represents Relevance Zone 1, but this same zone also serves as a Detection Zone for
Relevance Zone 2 and so on.
6 © ISO 2020 – All rights reserved

Figure 3 — Concatenated Relevance Zones
5.2 Location referencing
5.2.1 General
There are essentially two different ways of referencing road locations (refer to ISO 17572-1):
— map-based location referencing, when referencing attributes of the road network itself;
— geographic location referencing, when referencing a regular or irregular division of space which
exists independent of the representation of the road network.
5.2.2 Geographic positioning
Geographic location systems or coordinate systems are location maps composed of imaginary,
intersecting lines forming a grid. Coordinate values of the grid, expressed as numeric or alphanumeric
characters, are used to describe a position.
To translate position data expressed in longitude, latitude, and height to the corresponding real position
on earth or vice-versa, the earth-centred, earth-fixed, polar-coordinate geodetic datum WGS84 (G1150)
shall be used (see NIMA TR8350.2, ed.3). Alternatively, any earth-centred, earth-fixed polar coordinate
geodetic datum can be used as long as the maximum datum displacement relative to the geodetic datum
agreed on, or relative to WGS84 (G1150) in case of no agreement, is acceptable to the application.
NOTE A suggested tolerance of 0,3 m in datum displacement (also called datum shift) is intended, for
example, to allow for using the International Terrestrial Reference Frame (ITRF) or the European Terrestrial
Reference Frame (ETRF) geodetic datum as alternative to the WGS84. Datum displacements can be calculated
according to the definitions in ASME Y14.5-2009.
An ITS-S sending an IVI Structure provides one or more Reference Point(s). The Reference Point can be
the reference for the description of a static zone or a dynamic (moving) zone. The zone can be described
by a polygonal line which delineates a segment or an area or can be described by a distance value
indicating the extension of the relevance zone from the Reference Position and the heading relative to
the Reference Position.
The detection zone can optionally be provided as a polygonal line in approach to the Reference Position.
If the Reference Position is the position of a moving object, the polygonal line is represented by the last
positions of the path of the moving object (e.g. the trace of a roadworks vehicle).
Determining the relevance of IVI is carried out by referencing the location of a receiving ITS-S relative
to a reference in a coordinate-based system.
As a vehicle progresses, its motion creates a series of points. The series, when assembled as a set, trace
the path of the vehicle. The path enables a receiving ITS-S to detect the applicability of a Relevance Zone
and the approach into a Relevance Zone.
5.2.3 Map-based location referencing
This document supports map-based location referencing, by reference to a link ID in a digital map
database (the “map”). The supported map is the Map Data Message (MAP) defined in ISO/TS 19091.
This can also be a MAP Extended Message as defined in ETSI/TS 103 301.
An ITS-S sending an IVI Structure provides one or more references to Map Data Messages. The Map
Data Message can either represent an intersection: this is when the option intersections is used. Or
the Map Data Message can represent a road segment: this is when the option roadSegments is used. The
reference to the Map Data Message includes the type of option that is referred to.
A zone can be described with reference to one or more links defined in the Map Data Message. The link
ID in such a message is called LaneID.
Determining the relevance of IVI is carried out by referencing the location of a receiving ITS-S relative
to the links in the Map Data Message.
6 IVI Containers
6.1 IVI Management Container
6.1.1 Definition
IVI Management Container contains information regarding the management of the IVI Structure which
supports the receiving ITS-S to deal with the lifecycle of the IVI. It includes information which allows
receiving ITS stations to identify further processing. Table 1 describes the contents for inclusion in the
IVI Management Container. The syntax is defined in Annex A as mandatory component of the data type
IviStructure of type IviManagementContainer.
8 © ISO 2020 – All rights reserved

Table 1 — IVI Management Container
a
Container Component M/O Description
serviceProviderId
IVI Management M Identifies the organization that provided the
Container IVI
by using the DF Provider.
iviIdentificationNumber
M Identifier of the IVI Structure, as assigned by
the Service Provider using the DE
IviIdentificationNumber.
timeStamp
O Timestamp of the generation or last change of
information content using the DE
TimestampIts imported from ETSI/
TS 102 894-2.
validFrom
O Start time of the validity period of the mes-
sage using the DE TimestampIts imported
from ETSI/TS 102 894-2.
validTo
O End time of the validity period of the message
using the DE TimestampIts imported from
ETSI/TS 102 894-2.
connectedIviStructures
O List of other iviIdentificationNumber
identifying other IVI Structures of the same
authority which are connected to the IVI
Structure using the DE
IviIdentificationNumber.
iviStatus
M Status of the IVI Structure using the DE
IviStatus.
connectedDenms
Extension to the O List of ids of DENMs which are semanti-
management cally connected to the IVI, using the DF
container ConnectedDenms.
a
Mandatory (M) shall be included in the container. Optional (O) may be included in the container.
6.1.2 Usage — IVI Management Container
The sending ITS-S shall include the components serviceProviderId and iviIdentificationNumber, and
it can include the component timeStamp.
The iviIdentificationNumber in the IVI Management Container is assigned by the Service Provider
and should be retained as long as the IVI Structure e
...