ISO 15075:2003

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

• Status: Published
• Publication Date: 02-Dec-2003
• ICS: 35.240.60 - IT applications in transport
• ICS: 43.040.15 - Car informatics. On board computer systems
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204 - Intelligent transport systems
• Current Stage: 9093 - International Standard confirmed
• Completion Date: 29-Jul-2022

Relations

• Consolidated By: ISO/IEEE 11073-10418:2014 - Health informatics — Personal health device communication — Part 10418: Device specialization — International Normalized Ratio (INR) monitor
• Effective Date: 06-Jun-2022

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 15075:2003(E)
©
ISO 2003

---------------------- Page: 1 ----------------------
ISO 15075:2003(E)
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 [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO 2003 — All rights reserved

---------------------- Page: 2 ----------------------
ISO 15075:2003(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
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.

© ISO 2003 — All rights reserved iii

---------------------- Page: 3 ----------------------
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
© ISO 2003 — All rights reserved 1

---------------------- Page: 4 ----------------------
ISO 15075:2003(E)
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

---------------------- Page: 5 ----------------------
ISO 15075:2003(E)
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
© ISO 2003 — All rights reserved 3

---------------------- Page: 6 ----------------------
ISO 15075:2003(E)
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

---------------------- Page: 7 ----------------------
ISO 15075:2003(E)
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

© ISO 2003 — All rights reserved 5

---------------------- Page: 8 ----------------------
ISO 15075:2003(E)
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

---------------------- Page: 9 ----------------------
ISO 15075:2003(E)
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
(Applicable
to beacons
Beacon location
only)
— standard location reference (1) l 64 F
— offset from reference point (1 m resolution) l 16 F
14L Position IN Message code l 16 F
report from
from Beacon pair Identification (site Identification) (40)
RS beacon
RS
(verbal
— controller number l 8 F
references)
— first beacon's (location) ID number l 16 F
(Applicable
— second beacon's ID (supplied in pairs) l 16 F
to beacons
only)
Beacon number (site Identification) (1 or 24) V
— beacon controller number l 8
— extension number (0 = end of repetition) l 1 F
— beacon (location) ID number l 15 F
Beacon location
— map version l 16 F
— standard location reference for the beacon (1) l 64 F
— road type l 2 F
— link number l 12 F
— road name
— number of characters for display: o l 8 F
— number of characters for phonetic output: p l 8 F
— road name for display l 8*o V
— road name for phonetic output l 8*p V
— point name:
— number of characters for display: q l 8 F
— number of characters for phonetic output: r l 8 F
— point name for display A 8*q V
— point name for phonetic output A 8*r V
© ISO 2003 — All rights reserved 7

---------------------- Page: 10 ----------------------
ISO 15075:2003(E)
Table 1 (continued)
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
15L Differential IN Message code l 16 F
GPS position
Use results of ISO GPS interface standards efforts — — —
correction
factors
16L General text IN Message code l 16 F
messages or
Message priority code l 4 F
OUT
Message time stamp (1 s resolution) l 17 F
Code for type of information l 16 F
Message character type (1 or 2 bytes) — l 1 F
to accommodate oriental characters
Number (N) of characters in the text message. l 7 F
Limit N u 120 (60 for oriental)
Text message l N* (8 or 16) F
17L Advisory IN Message code l 16 F
messages
Sequence number l 11 F
(traffic,
Message time stamp (1 s resolution) l 17 F
safety,
weather)
Number (N) of advisory codes being reported in the l 5 F
message
{repeated group: N times}
— code for type of advisory (such as RDS-TMC) l 5 F
— codes for clarifying advisory information (such as l V V
Alert C or Alert + protocol)
— duration
— severity
— region
— other
NOTE The vehicle must have a message code database
in order to translate the codes.
18L Request for OUT Message code l 16 F
advisory
Assigned vehicle ID l 40 F
messages
Billing ID l 40 F
(traffic,
safety,
Region ID (standard referencing) (1) l 32 F
weather)
Type of information being requested l 5 F
19L Vehicle IN Message code l 16 F
transportation
Number (N) of transports being reported in the l 5 F
information
message
(such as car
{repeated group: N times}
train or car
— standard location reference for departure point (1) l 64 F
ferry)
— standard location reference for arrival point (1) l 64 F
— travel time (1 min resolution) l 16 F
— cost
— currency code l 5 F
— currency units (hundredths) l 12 F
— carrier ID l 30 F
Number (n) of departure times being reported l 4 F
{second repeated group: n times}
— departure times (1 min resolution) l 16 F
— capacity/availability l 6 F
8 © ISO 2003 — All rights reserved

---------------------- Page: 11 ----------------------
ISO 15075:2003(E)
Table 1 (continued)
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
20L Park & ride IN Message code l 16 F
information
Number (N) of locations being reported in the message l 5 F
{repeated group: N times}
— standard location reference for departure point (1) l 64 F
— code for transportation mode l 3 F
— code for route l 6 F
— travel time (1 min resolution) l 10 F
— cost
— currency code l 5 F
— currency units (hundredths) l 12 F
— carrier ID l 10 F
Number (n) of departure times being reported l 5 F
{second repeated group: n times}
— departure times (1 min resolution) l 16 F
— capacity/availability l 6 F
Number (M) of route way-points being reported l 6 F
{third repeated group: M times}
— standard location references for route way-points (1) l 64 F
21L General IN Message code l 16 F
parking
Message time stamp (1 s resolution) l 17 F
information
message
Number (N) of parking locations (lots) being reported l 16 F
{repeated group: N times}
— standard location reference for the parking location l 64 F
(point(1))
— capacity of the parking place l 8 F
— name of the parking place
— number of characters for display: o l 8 F
— number of characters for phonetic output: p l 8 F
— parking place for display A o*8 V
— parking place for phonetic output A p*8 V
— road name where parking entrance is located
— number of characters for display: q l 8 F
— road name for display A q*8 V
— number of available parking spaces in the lot l 8 F
— estimated waiting time for next open parking space l 8 F
(min)
— fee information l 16 F
— business hours l 16 F
— entrance information l 40 F

© ISO 2003 — All rights reserved 9

---------------------- Page: 12 ----------------------
ISO 15075:2003(E)
Table 1 (continued)
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
22L Request for OUT Message code l 16 F
parking
Assigned vehicle ID l 40 F
information
Billing ID l 40 F
Standard location reference for the destination (point) (1) l 32 F
Type of information being requested l 5 F
23L Response to IN Message code l 16 F
request for
Assigned vehicle ID l 40 F
parking
information Message time stamp (1 s resolution) l 17 F
Number (N) of parking locations (lots) being reported l 16 F
{repeated group: N times}
— standard location reference for the parking location l 64 F
(point(1))
— capacity of the parking place l 8 F
— name of the parking place
— number of characters for display: o l 8 F
— number of characters for phonetic output: p l 8 F
— parking place for display A o*8 V
— parking place for phonetic output A p*8 V
— road name where parking entrance is located
— number of characters for display: q A 8 F
— road name for display l q*8 V
— number of available parking spaces in the lot l 8 F
— estimated waiting time for next open parking space l 8 F
— fee information l 16 F
— business hours l 16 F
— entrance information l 40 F
24L Navigation IN Message code l 16 F
database
Sequence number l 11 F
updates
Region ID (standard referencing) (1) l 32 F
(changes
and
City ID (standard referencing) (1) l 16 F
additions)
Database version being modified l 6 F
Number (N) of database changes in this message l 5 F
{repeated group: N times}
— modification code (such as: change attributes on l 5 F
existing link(s); add a new link(s); delete an existing link;
or add a hotel)
— size code for information field l 7 F
— updated information l,A V V

IF CHANGES ARE TIED TO LINKS, ADD THE
FOLLOWING:
— number (n) of links receiving the specified l 5 F
modification
{second repeated group: n times}
— standard location references for the links (1) l 64 F
10 © ISO 2003 — All rights reserved

---------------------- Page: 13 ----------------------
ISO 15075:2003(E)
Table 1 (continued)
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
25L Request for OUT Message code l 16 F
navigation
Assigned vehicle ID l 40 F
database
updates
Billing ID l 40 F
Region ID (standard referencing) (1) l 32 F
City ID (standard referencing) (1) l 16 F
Database version being modified l 6 F
26L Regional IN Message code l 16 F
system
Date (7 bits for year, 4 for month, 5 for day) l 16 F
status
reports
Message time stamp (1 s resolution) l 17 F
Region ID (standard referencing) (1) l 32 F
City ID (standard referencing) (1) l 16 F
Database version l 6 F
Field definition code for the following global time change l 3 F
codes
Global travel time change codes
— roadway classification codes l V V
— travel time factors or filters l V V
27L TMC network IN Message code l 16 F
status report
Message time stamp (1 s resolution) l 17 F
Text message
— number of characters for display: o l 8 F
— number of characters for phonetic output: p l 8 F
— text message for display A o*8 V
— text message for phonetic output A p*8 v
ID of reporting subsystem
— type of subsystem l 8 F
— subsystem controller ID l 32 F
Status code l 8 F
Equipment failures
— number (N) of equipment failures l 8 F
— failed equipment IDs l N*32 V
28L Status IN Message code l 16 F
request to
Application code l 6 F
vehicle's
communi-
Application specific ID l 40 F
cation
Test sequence number l 6 F
system
Message time stamp (1 s resolution) l 17 F
Code for requested test (such as communication, l 8 F
navigation, etc.)

© ISO 2003 — All rights reserved 11

---------------------- Page: 14 ----------------------
ISO 15075:2003(E)
Table 1 (continued)
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
l 16 F
29L Vehicle OUT Message code
response to
Application code l 6 F
communi-
cation
Application specific ID l 40 F
system
l 6 F
status Test sequence number
request
l 17 F
Message time stamp (1 s resolution)
Code for test being reported (defines results field format) l 10 F
Test results l V V
l 16 F
30L Dynamic IN Message code (from TMC or RS beacon)
incident
l 6 F
Sequence number
reports from
TMC
Message time stamp (1 s resolution) l 17 F
Number (N) of incidents being reported in the message l 5 F
{repeated group: N times}
— type of incident l 12 F
— standard location reference for the link (1) l 64 F
l 2 F
— cause code type
l 6 F
— cause code (optional)
— time of incident l 17 F
— expected incident ending time l 17 F
l 16 F
31L Dynamic IN Message code (from TMC or RS beacon)
incident
l 6 F
Sequence number for the incident
report from
TMC
Message time stamp (1 s resolution) l 17 F
(detailed)
Link layer l 2 F
l 4 F
Type of cause code being used
l 8 F
Cause starting time
Cause information (V)
— number of characters for display: o l 8 F
A o*8 V
— cause information for display
l
Main incident type 4 F
Secondary incident type (optional) l 8 F
Starting time of incident l 17 F
l
Ending time of incident 17 F
l
Distance from end of starting link (0,1 mile increments) 8 F
Distance from end of ending link (0,1 mile increments) l 8 F
State of congestion l 4 F
l
Recovery information 22 F

12 © ISO 2003 — All rights reserved

---------------------- Page: 15 ----------------------
ISO 15075:2003(E)
Table 1 (continued)
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
l 8 F
  Number (N) of links being reported in the message
{repeated group: N times}
l 64 F
— standard location reference for the link (1)
— name of the incident location (point) on the link (V)
— number of characters for display: p l 8 F
— number of characters for phonetic output: q l 8 F
A p*8 V
— location for display
A q*8 V
— location for phonetic output
— road name of the link (V)
— number of characters for display: r l 8 F
l 8 F
— number of characters for phonetic output: s
A r*8 V
— road name for display
— road name for phonetic output A s*8 V
— directional code l 4 F
l 14 F
— distance of incident from link starting point (0,1 mile
increments)
32L Status OUT Message code l 16 F
request to
l 40 F
Assigned vehicle ID
TMC/RS
com. system
l 8 F
Code for requested test
33L Status IN Message code l 16 F
response
Assigned vehicle ID l 40 F
from
TMC/RS
l 6 F
Test sequence number
com. system
l 17 F
Message time stamp (1 s resolution)
Code for test reported (defines results field format) l 10 F
Test results l V V
© ISO 2003 — All rights reserved 13

---------------------- Page: 16 ----------------------
ISO 15075:2003(E)
Table 2 — Additional messages used by centrally determined route guidance systems
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
1C Request for OUT Message code I 16 F
routing
Assigned vehicle ID I 40 F
(general)
Origin (or current location)
— standard location reference for a point (1) I 64 F
— offset from reference point (20 m resolution) I 8 F
Destination designation code (1 = standard location I 4 F
reference; 2 = zones; 3 = area specific location codes:
Type A, B, C or D)
— If 1: standard location reference for a point (1) I 64 F
— If 2: zones [standard location reference for an area I 64 F
(1)]
— If 3A: uniquely designated links (requesting route to (34)
designated link):
— code for area in which link is located I 20 F
— code for type of road (general or limited access) I 2 F
— link number I 12 F
— If 3B: selectively designated links (requesting (34)
whichever is better of two; one is route to designated link
and the other, route with link which is in opposite
direction to designated link and taken as designated):
— code for area in which backward link is located I 20 F
— code for type of road (general or limited access) I 2 F
— link number I 12 F
— If 3C: roadway Intersections (nodes): (34)
— code for area in which node is located I 20 F
— code for type of road (general or limited access) I 2 F
— node number (link connected to the node) I 12 F
— If 3D: zones within a larger area: (34)
— code for area in which zone is located I 20 F
— zone number I 14 F
Number (N) of constraint codes: If N = 15, then an 8 bit I 4 F
constraint flag follows {repeated group: N times}
8*N
Routing constraint code (for example, no tolls, no I V
freeways, scenic routing, trucks, hazardous materials,
(8 IF
emergency vehicles, directional restrictions, high
N=15)
occupancy vehicles, or multimodal)


14 © ISO 2003 — All rights reserved

---------------------- Page: 17 ----------------------
ISO 15075:2003(E)
Table 2 (continued)
Item Data Field Required Field
Message Data fields comprising the message
No. flow type field size format
2C Request for OUT Message code l 6 F
RS beacon
Assigned vehicle ID l 40 F
routing
Destination designation code (1 = standard location l 4 F
(Applicable
reference; 2 = zones; 3 = area specific location codes:
to beacons
Type A, B, C or D)
only)
— If 1: standard location reference for a point (1) l 64 F
— If 2: zones (standard location reference for an area l 64 F
(1))
— If 3A: uniquely designated links (requesting route to (34)
designated link):
— code for area in which link is located l 20 F
— code for type of road (general or limited access) l 2 F
— link number l 12 F
— If 3B: selectively designated links (requesting (34)
whichever is better of two: one is route to designated link
and the other, route with link which is in opposite
direction to des
...