ISO 15075:2003
(Main)Transport information and control systems — In-vehicle navigation systems — Communications message set requirements
Transport information and control systems — In-vehicle navigation systems — Communications message set requirements
ISO 15075:2003 specifies message content and format utilized by in-vehicle navigation systems. Its emphasis is on messages that are required to generate or enhance routing instructions. There is a particular focus on messages that would not necessarily be included in a more general traffic management message list. Although ISO 15075:2003 emphasizes requirements for Locally Determined Route Guidance (LDRG) systems that utilize on-vehicle map databases, it also includes messages that would be utilized primarily by Centrally Determined Route Guidance (CDRG) systems and certain value-added messages.
Systèmes de commande et d'information des transports — Systèmes de navigation dans les véhicules — Exigences relatives à l'ensemble des messages des communications
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 15075
First edition
2003-12-01
Transport information and control
systems — In-vehicle navigation
systems — Communications message
set requirements
Systèmes de commande et d'information des transports — Systèmes
de navigation dans les véhicules — Exigences relatives à l'ensemble
des messages des communications
Reference number
©
ISO 2003
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2003
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2003 — All rights reserved
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
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.
ISO 15075 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
INTERNATIONAL STANDARD ISO 15075:2003(E)
Transport information and control systems — In-vehicle
navigation systems — Communications message set
requirements
1 Scope
This International Standard specifies message content and format utilized by in-vehicle navigation systems. Its
emphasis is on messages that are required to generate or enhance routing instructions. There is a particular
focus on messages that would not necessarily be included in a more general traffic management message list.
Although this International Standard emphasizes requirements for Locally Determined Route Guidance
(LDRG) systems that utilize on-vehicle map databases, it also includes messages that would be utilized
primarily by Centrally Determined Route Guidance (CDRG) systems and certain value-added messages.
2 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
2.1
Locally Determined Route Guidance System
LDRG
system which provides a driver with step-by-step driving instructions that are determined by an on-vehicle
system
NOTE The system typically consists of a display screen, a computer, routing and guidance software, a navigable
map database, and positioning equipment to track the vehicle's location as it proceeds along its path.
2.2
Centrally Determined Route Guidance System
CDRG
system which provides a driver with step-by-step driving instructions that are similar to those offered by a
LDRG
NOTE With a centrally determined system, the routing instructions are determined at an off-vehicle location and
transmitted to the vehicle.
2.3
message
data element which is formatted for transmission and broadcast by means of electromagnetic field
propagation
2.4
standard location references
standardized method for referencing geographic locations including points, links between points and
1)
geographic areas
2.5
traffic message centre
TMC
centre that transmits (receives) messages to (from) the vehicle by any communication means other than short
range, vehicle-to-roadside communications (beacons)
NOTE The bulk of these messages are expected to be traffic related.
2.6
roadside beacon
RS
short-range vehicle-to-roadside communication device with the inherent location feature that if the vehicle is
receiving the signal, then the vehicle has to be positioned in a specific, localized area
3 Message set: Contents and format
The messages in this International Standard are divided into three categories, as follows.
Messages that are required by route guidance systems to determine their recommended routes on-board
the vehicle (LOCALLY DETERMINED). These address a wide range of information such as traffic
conditions, tolls, road construction and availability of parking.
Messages that are required by route guidance systems for which routes are determined off-board the
vehicle (CENTRALLY DETERMINED). These primarily focus on requesting and transmitting routing
information.
VALUE-ADDED messages that could be displayed by an in-vehicle navigation system, routed through a
system, or utilized by a system in providing guidance. These include messages for communicating
information regarding items such as emergencies, toll and fee payments, and ridesharing.
Tables 1, 2 and 3 consist of message contents and formats for locally determined route guidance systems,
centrally determined route guidance systems, and value-added messages. The structure of the tables is as
follows.
Item number: The alphanumeric number assigned to a message by ISO/TC 204. This signifies the
message's relative position in the list and its classification:
L = LDRG; C = CDRG; V = value added
Message: A brief description of the message.
Data flow: IN means flow into the vehicle (navigation system) from the infrastructure (communication
device); OUT means flow to the infrastructure (communication device) from the vehicle (navigation
system). See Figure 1.
1) ITS standards for location referencing are being developed within both CEN/TC 278, SWG 7.3, and ISO/TC 204,
SWG 3.3. Oak Ridge National Laboratories in the US are working on a standard location message protocol. Japan utilizes
a standard referencing system devised by the Japan Kokudo-Chiri-In. The field size estimates for location references in
this International Standard are based on preliminary drafts from these efforts.
2 © ISO 2003 — All rights reserved
Data fields comprising the message: Description of the specific data fields required for the message.
Note that this International Standard uses the same data fields in a modular way to create different
messages.
Field type: A = alphanumeric; F = floating point; I = integer; V = variable
Required field size: Specified in bits.
Field format: F = fixed length; V = variable length
Key
1 communication device
2 in-vehicle application
3 navigation system
a
In
b
Out
Figure 1
Table 1 — Messages used by locally determined route guidance systems
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
1L Dynamic link IN Message code [general use by TMC or roadside (RS) l 16 F
times from beacon]
traffic
Sequence number l 6 F
message
centre (TMC)
Message time stamp (1 s resolution) l 17 F
Data format code [congestion levels, link travel times, l 3 F
travel time deltas, or time/speed factors (ratios)].
Number (L) of 5 min time segments per link (L u 6)l 3 F
(1st = current; 2nd = predicted 5 min later; etc.)
Standard location reference for a geographic area (1) l 64 F
Number (N) of links being reported in the message l 8 F
{repeated group: N times}
— standard location reference for the link (1) l 64 F
— cause code type (2 bits: 00 = not specified) l 2 F
— cause code (optional) l 6 F
{repeated group: L times}
Travel information for 5 min interval l V V
2L Dynamic link IN Message code (for use by RS beacons) l 16 F
times from
from Sequence number l 6 F
roadside
RS
beacons
Message time stamp (1 s resolution) l 17 F
(RS)
Beacon pair identification (40)
— controller number l 8 F
(Applicable
to beacons — first beacon (location) ID number l 16 F
only)
— second beacon's ID (for information supplied in pairs) l 16 F
Data format code [congestion levels, link travel times, l 3 F
travel time deltas, or time/speed factors (ratios)]
Number (L) of 5 min time segments per link (L u 6) l 3 F
Number (N) of links being reported in the message l 8 F
{repeated group: N times}
— standard location reference for the link (1) l 64 F
— cause code type (2 bits: 00 = not specified) l 2 F
— cause code (optional) l 6 F
{repeated group: L times}
Travel information for 5 min interval l V V
3L Request for OUT Message code (from vehicle to TMC or RS beacon) l 16 F
temporary
Transaction number (random) chosen by vehicle l 16 F
vehicle ID
4 © ISO 2003 — All rights reserved
Table 1 (continued)
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
4L Assignment IN Message code (from TMC or RS beacon to vehicle) l 16 F
of temporary
Transaction number sent by the vehicle l 16 F
vehicle ID
Temporary vehicle ID assigned by TMC or RS beacon (40)
— flag indicating ID was assigned by TMC (0) or RS l 1 F
beacon (1)
— asssigned vehicle ID l 39 F
NOTE Japan uses the transaction number as the first
16 bits and then adds 23 bits as a beacon assigned ID.
5L Vehicle OUT Message code (general use to TMC or RS beacon) l 16 F
probe reports
Assigned vehicle ID l 40 F
(database
link travel
Link database version l 4 F
times)
Number (N) of links being reported in the message l 8 F
{repeated group: N times}
— standard location reference for the link (1) l 64 F
— cause code type (2 bits: 00 = not specified) l 2 F
— cause code [optional: “time-out” while on link, ignition l 5 F
off while on link, traffic patterns (TBD codes)]
— travel time (in s) l 12 F
— waiting (stopped) time (in s); FFF means no data are l 12 F
available
— end-of-link travel time stamp (1 s resolution) l 17 F
6L Vehicle OUT Message code (general use to TMC or RS beacon) l 16 F
probe reports
Assigned vehicle ID l 40 F
(beacon-to-
beacon
Vehicle measured travelling time (from previous location (40)
travel times)
(beacon)
— beacon number (site Identification) for previously (24)
passed beacon
— beacon controller number l 8 F
— beacon (location) ID number l 16 F
— vehicle determined elapsed travel time (in s) between l 16 F
beacon
Table 1 (continued)
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
7L Probe IN Message code l 16 F
exception
Number (N) of exception rules reported in this message l 5 F
reporting
{repeated group: N times}
rules (may
vary by
— exception rule code (1, 2, 3 or 4) l 2 F
roadway
IF 1 (roadway type):
type, zones,
links, etc.)
— roadway type code l 4 F
— threshold value l 6 F
IF 2 (zone):
— zone code ID l 11 F
— threshold value l 6 F
IF 3 (links):
— Number (n) of links in the message l 6 F
{repeated group: n times}
— standard location reference for the link (1) l 64 F
— threshold values l 6 F
IF 4 (global):
— thresholds for the whole system l 6 F
8L Request for IN Message code l 16 F
origin,
Assigned vehicle ID l 40 F
destination
and route
9L Reporting IN Message code l 16 F
origin,
Assigned vehicle ID l 49 F
destination
and route
Origin
— standard location reference (1) l 64 F
Destination
— standard location reference (1) l 64 F
Number (N) of en route links being reported l 16 F
(00 = No route reported)
{repeated group: N times}
— standard location references for the links (1) l N*64 F
NOTE This message can be used to report origin-
destination pair and (optional) planned route for either locally or
centrally determined systems.
10L Report of trip OUT Message code l 16 F
completion
Assigned vehicle ID l 40 F
Origin
— standard location reference (1) l 64 F
Destination
— standard location reference (1) l 64 F
Travel time (1 min resolution) l 16 F
6 © ISO 2003 — All rights reserved
Table 1 (continued)
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
11L Request for IN Message code l 16 F
vehicle's
Assigned vehicle ID l 40 F
current
position
12L Reporting OUT Message code l 16 F
current
Assigned vehicle ID l 40 F
vehicle
position
— standard location reference for current vehicle l 64 F
position (1)
13L Position IN Message code l 16 F
report from
from Beacon pair identification (site identification) (40)
RS beacon
RS
(standard
— controller number l 8 F
location
— first beacon's (location) ID number l 16 F
reference)
— second beacon's ID (supplied in pairs) l 16 F
(Applicabl
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.