CEN/TS 14821-3:2003

SLOVENSKI STANDARD
01-oktober-2003
3URPHWQHLQSRWRYDOQHLQIRUPDFLMH77,6SRURþLOD77,SUHNFHOLþQLKRPUHåLM±
GHO2VQRYQLLQIRUPDFLMVNLHOHPHQWL
Traffic and Travel Information (TTI) - TTI messages via cellular networks - Part 3: Basic
information elements
Verkehrs- und Reiseinformationen (TTI)-TTI-Nachrichten über mobile - Teil 3:
Grundlegende Informationselemente
Ta slovenski standard je istoveten z: CEN/TS 14821-3:2003
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

TECHNICAL SPECIFICATION
CEN/TS 14821-3
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
May 2003
ICS 35.240.60
English version
Traffic and Travel Information (TTI) - TTI messages via cellular
networks - Part 3: Basic information elements
This Technical Specification (CEN/TS) was approved by CEN on 10 May 2001 for provisional application.
The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their
comments, particularly on the question whether the CEN/TS can be converted into a European Standard.
CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available. It
is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final decision about the possible
conversion of the CEN/TS into an EN is reached.
CEN members are the national standards bodies of Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece,
Hungary, Iceland, Ireland, Italy, Luxembourg, Malta, Netherlands, Norway, Portugal, Slovakia, Spain, Sweden, Switzerland and United
Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: rue de Stassart, 36  B-1050 Brussels
© 2003 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 14821-3:2003 E
worldwide for CEN national Members.

Table of contents
PAGE
TABLE OF CONTENTS 2
FOREWORD 4
INTRODUCTION 5
1. SCOPE 6
2. NORMATIVE REFERENCES 7
3. DEFINITIONS AND ABBREVIATIONS 8
3.1 Definitions 8
3.2 Abbreviations 10
4. GENERAL DEFINITIONS AND INFORMATION ELEMENTS 15
4.1 Absolute Time 15
5. AREA AND LOCATION CODING 17
5.1 General Format 17
5.2 WGS 84 17
5.3 ILOC 25
5.4 TMC-Location 25
6. COMMUNICATION ADDRESS 27
6.1 Network ID 28
6.2 Validity Range of Address 28
6.3 Flag BCD/ASCII 29
6.4 Address Length 29
6.5 Address 29
7. TEXT AND TRANSPARENT DATA 30
7.1 Format of a Text Element 30
8. EXTENDED LOCATION BLOCK 34
8.1 Number of ELB-Waypoints - 134
8.2 Time Difference between Generation Time and ELB-Waypoint 1 34
8.3 ELB-Waypoint X 34
8.4 Flag: GPS Raw Data Present 37
8.5 GPS Raw Data 37
9. BREAKDOWN REASONS 39
10. MASTER DATA 43
10.1 Colour of Vehicle 43
10.2 Vehicle Identification Number - VIN 43
10.3 Vehicle Model 43
10.4 Year of Construction 43
10.5 Licence Plate 43
11. GEOCODES - CONTENTS AND STRUCTURING OF TERMINAL TABLES 44
11.1 Coverage of terminal table 44
11.2 Coding table for terminal devices 44
11.3 Geocoding 55
12. EVENT CODES 58
12.1 Introduction 58
12.2 Description of the event code structure 58
12.3 Quantifiers 58
12.4 Description of the terminal device table 59
12.5 Assignment of Event Codes and Quantifiers 60
13. CODING OF NUMBERS 75
13.1 Unsigned Integers 75
13.2 Signed Integers 75
13.3 Binomially Coded Numbers 75
14. SPECIFICATION IN ASN.1 76
BIBLIOGRAPHY 91
Foreword
This document(CEN/TS 14821-3:2003) has been prepared by Technical Committee CEN/TC 278 " Road
transport and traffic telematics ", the secretariat of which is held by NEN, in collaboration with Technical
Committee ISO/TC 204 " Transport information and control systems ".
This was prepared by Working Group 7 of CEN TC278. In the field of Traffic and
Technical Specification
Traveller Information, the innovative rate is high, with many research and development projects under way
in many countries, and there is a need to establish prospective standards which allow manufacturers to
introduce competitive products to the market in the knowledge that they can accommodate the future issues
of the standard(s) without fundamental change to equipment.
No known national s (identical or conflicting) exist on this subject.
Technical Specification
CEN/TS 14821 consists of eight parts; one part describing the framework and seven parts providing
detailed specifications of all components, protocols and services that are within the scope of CEN/TS
14821.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to announce this Technical Specification: Austria, Belgium, Czech Republic, Denmark,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Luxembourg, Malta, Netherlands,
Norway, Portugal, Slovakia, Spain, Sweden, Switzerland and the United Kingdom.
Introduction
Traffic and Traveller Information (TTI) may be disseminated through a number of services or means of
communication, covering static displays, portable terminals and in-vehicle equipment.
For all such services, the data to be disseminated, and the message structure involved in the various
interfaces, require clear definition and standards formats in order to allow competitive products to operate
with any received data.
This  focuses on an application data specification whereby data is produced at a
Technical Specification
central location and is disseminated via a cellular radio network. It addresses the data specifications for
both downlink and uplink existing between a central location and randomly located vehicles. It enables
messages to be exchanged between different systems and service providers adopting a variety of
applications specifications.
Other s are being produced by the CEN TC278 Working Group 4 to cover TTI
Technical Specification
dissemination via other means or services. This set of specifications is named GATS (Global Automotive
Telematics Standard). GATS provides the modular framework for implementing such traffic telematics
services on an open technology platform and is network - independent. In many details definitions are
necessary to ensure interoperability. Therefore, those detailed definitions are given in CEN/TS 14821-8.
With the development of future mobile communication systems towards UMTS / IMT2000 the bottleneck of
narrow-band data communication might fade. Due to its modular structure, the GATS framework and
applications are prepared for that due to its network-independence. The same holds for emerging
technologies for positioning which today is almost exclusively based on GPS.
Other relevant standard developments are, independent from telematics, the application-independent
Wireless Application Protocol (WAP), enabling mobile access to the Internet. It is understood that these
emerging technologies might fit into the framework of telematics applications in future WAP-versions. For
the time being, GATS already today independently from WAP enables access to telematics services.
Utilisation of GATS on a WAP protocol stack and identifying necessary adaptation of WAP specifications (if
any) is currently under investigation of the appropriate groups within WAP-Forum and GATS-Forum.
1. Scope
This  defines the specific interfaces and functionality of traffic telematics (TT)
Technical Specification
services based on the use of cellular networks. Device manufacturers are enabled to develop terminal
equipment compatible to services based on this . This will allow for interoperability of
Technical Specification
different terminal equipment and service providers which allows competition between service providers and
terminal manufacturers. Furthermore it sets the scene for international availability of these services.
This  specifies
Technical Specification
• TT-specific interfaces between terminal and service centre. This especially incorporates the message
sets of the application data protocols and the service-independent communication handling (including
conditional access and transport protocols).
• Functionality, procedures and requirements of basic terminal components as well as their interaction
with the service centre. This especially comprises conditional access and security mechanisms.
• Service Specifications, which are essential to ensure consistent behaviour of terminal and service
centre.
The services incorporated within this issue comprise:
• breakdown and emergency services

• interactive traffic information services
• broadcast traffic information services
• navigation services (route assistance, route advice, homing)
• operator services
• general information services

• floating car data collection
It is envisaged that future research and development will lead to improvements on the services listed above
as well as to the creation of new services. Nevertheless this Technical Specification provides the framework
for seamless integration of new features and services into the existing architecture.
2. Normative references
This incorporates by dated or undated reference, provisions from other publications.
Technical Specification
These normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply
to this only when incorporated in it by amendment or revision. For undated
Technical Specification
references the latest edition of the publication referred to applies.
EN ISO 14819-2 Traffic and Traveller Information (TTI) - TTI Messages via traffic message coding -
Part 2: Event and information codes for Radio Data System - Traffic Message Channel (RDS-TMC) (ISO
14819-2:2003)
3. Definitions and abbreviations

3.1 Definitions
For the purposes of this Technical Specification, the following terms and definitions apply:
3.1.1 Attribute (of a Traffic Information Message)
A Traffic Information Message is made up of separate parts that can be called attributes. This includes, for
example, an item of information and a length of validity.
3.1.2 Authorisation
Reciprocal proof that the identity provided by the communications partner is valid
3.1.3 Broadcast Service
Data service within a cellular wireless network that allows for mono-directional dissemination of data from a
service centre to multiple users in the area of signal reception
3.1.4 Bypass Description
Representation of a Bypass, consisting of a Bypass Hint and/or a Bypass Route.
3.1.5 Bypass Hint
Representation of a hint for a Bypass
3.1.6 Bypass Link
Prominent waypoints on a Bypass Route
3.1.7 Bypass Route
Representation of the route for a Bypass
3.1.8 Cell Broadcast
Broadcast service of the GSM network
3.1.9 Data telegram
Digital message exchanged between two systems
3.1.10 Delivery Notification
Network acknowledgement for successful/ unsuccessful delivery of a message to the mobile device
3.1.11 Functional Road Class
A classification based on the importance of the road element in the connectivity of the total road network
3.1.12 Functional Road Class 0

Motorways
3.1.13 Functional Road Class 1
All non-Motorways that are part of a connection used for nation wide traffic and transport
3.1.14 Geocode
Geocodes are unique identifiers unmistakably defining important points on road networks. Geocodes can
be derived from / converted into WGS84 co-ordinates by the algorithm described in ENV ISO 14821 3.
3.1.15 Hardware service agents

Partner companies of the traffic telematics service providers who are authorised to install onboard
equipment into vehicles and to maintain it
3.1.16 Homing
Simple form of guidance to destination, in which the direction and
straight-line distance of the destination are indicated
3.1.17 Information Element
Information unit of a message
3.1.18 Intersection
Junction of two or more roads
3.1.19 Length of a Speech Report
Length of a Speech Report, including pauses, in tenths of a second
3.1.20 Mobile Originated
Data telegram sent from the onboard equipment to the Service Centre.
3.1.21 Mobile Terminated
Data telegram sent by the Service Centre to the onboard equipment.
3.1.22 Onboard equipment
A system, generally mobile, interacting with the service centre to handle traffic telematics services
3.1.23 Road Junction
Intersection of two or more roads
3.1.24 Route description
Description of a route showing the geometry of street intersections, manoeuvre instructions, street and
place names, and geographical co-ordinates
3.1.25 Service centre
System produced by the traffic telematics operators / service providers to handle traffic telematics services
3.1.26 Short Message Service
Packet-based form of data transfer within the GSM network
3.1.27 Speech connection
Communications channel between two systems for the bi-directional transmission of speech
3.1.28 Speech Report
Traffic Information Report transmitted by a speech system
3.1.29 Terminal Device
Generally mobile system interacting with the service centre for implementation of telematics services
3.1.30 TINFO
Traffic Information Report
3.1.31 TINFO Version
Unique identification of a Traffic Message, consisting of a number and a time stamp
3.1.32 Traffic Data
Data for qualification of Traffic Events. This includes:
Values: speed, traffic flow, traffic density
Places: position, place designation
Facts: description of situation
3.1.33 Traffic Event
An occurrence on a road or in an area that is worthy of reporting, such as a traffic jam, wrong-way driver, or
fog.
3.1.34 Traffic Information
Technical representation of a Traffic Situation within the onboard equipment, accomplished by a number of
Traffic Information Reports.
This Traffic Information can be displayed to the customer via suitable terminals.
3.1.35 Traffic Information Report
Technical representation of a Traffic Event produced by processing traffic data.
Each Traffic Reports uniquely identified by a number, the TINFO ID, a time stamp, the TINFO version.
Note: If the Traffic Event changes, the time stamp changes, but the TINFO ID number does not.
3.1.36 Traffic Situation
The total number of all Traffic Events taking place that deserve reporting within an area. The Traffic
Situation is always linked to an area. Thus, for example, an areas could be a conurbation or a geometrically
demarcated area; an example is the radius around a point.
3.1.37 Voice connection
Circuit-switched channel between two systems for bi-directional voice transmission
3.1.38 Waypoint
Significant points on the route
3.2 Abbreviations
For the purposes of this Technical Specification, the following abbreviations apply:
3.2.1 % ott
percent of the time
3.2.2 ADP
Application Data Protocol, i.e. a message set for a telematics service
3.2.3 AM
Acknowledge Message
3.2.4 ASN.1
Abstract Syntax Notation
3.2.5 BC
Broadcast
3.2.6 BCS
Broadcast Service
3.2.7 CA
Conditional Access
3.2.8 CAS
Conditional Access and Security
3.2.9 CB
Cellular Broadcast
3.2.10 CBC
Cipher Block Chaining
3.2.11 CLI
Calling Line Identification
3.2.12 CRM
Calling Request Message
3.2.13 CSD
Circuit Switched Data
3.2.14 DES
Data Encryption Standard: symmetrical encryption procedure
3.2.15 DRM
Digital Road Map
3.2.16 DSC
Data Service Centre: depending on the mobile communication network
3.2.17 ELB
Extended Location Block
3.2.18 FCD
Floating Car Data
3.2.19 FCDGM
FCD General Message
3.2.20 FCDPM
FCD Parameter Message
3.2.21 FCDNSM
FCD Notification Set-up Message
3.2.22 FCDRM
FCD Revoke Message
3.2.23 FCDVDSUM
FCD Virtual Detection Site Update Message
3.2.24 GATS
Global Automotive Telematics Standard
3.2.25 GEM
General Error Message
3.2.26 GPS
Global Positioning System NAVSTAR GPS
3.2.27 GSM
Global System for Mobile Communication
3.2.28 IE
Information Element
3.2.29 ICV
Initial Chaining Value
3.2.30 L_max
Max. length of transferable data in one data transaction
3.2.31 MAC
Message Authentication Code
3.2.32 MNA
Mobile Network Address
3.2.33 MF
Mandatory Fixed format
3.2.34 MO
Mobile Originated Message
3.2.35 MT
Mobile Terminated Message
3.2.36 MV
Mandatory Variable format
3.2.37 N_min
Minimum number of ELB waypoints
3.2.38 OBU
Onboard Unit, synonymously used telematics device, telematics terminal
3.2.39 OF
Optional Fixed format
3.2.40 OV
Optional Variable format
3.2.41 PDU
Protocol Data Unit
3.2.42 PFA
Probability of false alarm (i.e. estimated error is too large)
3.2.43 PMD
Probability of missed detection (i.e. estimated error is too small)
3.2.44 RSA
Asymmetrical encryption procedure by Rivest, Shamir and Adleman
3.2.45 SAE
Society of Automotive Engineers, Inc.
3.2.46 SMS
Short Message Service
3.2.47 SMSC
SMS Centre
3.2.48 SV
Space Vehicle
3.2.49 TEG
Telematics Expert Group – Group within the WAP-Forum Ltd.
3.2.50 TINFO
Traffic Information Report
3.2.51 TOC
Telematics Operator Code
3.2.52 TRP
Transport Protocol
3.2.53 TT
Traffic telematics
3.2.54 TTI
Traffic and Traveller Information
3.2.55 TTFF
Time to First Fix
3.2.56 UTC
Universal Time Co-ordinated
3.2.57 VDS
Virtual Detection Site
3.2.58 vel, V
Velocity
3.2.59 VIN
Vehicle Identification Number
3.2.60 WAP
Wireless Application Protocol
3.2.61 WGS84
World Geodetic System 84
4. General Definitions and Information Elements

4.1 Absolute Time
4.1.1 General
Absolute time stamps are transmitted in a unified format which allows to specify date and time with a
resolution of 1 second. The basis for the time referencing is UTC. Therefore time zones are not
distinguished.
Each time reference is given with the elements year, month, day (of month), hour, minute and second. The
coding of these elements is shown in the subsequent sections. The definition of bit order is given in 4.3.2 of
ENV 14821-1.
4.1.2 Year
Table 4-1: Coding Format for the Year IE
Value Coding Year
0 0 0 0 0 0 0 1990
1 0 0 0 0 0 1 1991




63 1 1 1 1 1 1 2053
4.1.3 Month
Table 4-2: Coding Format for the Month IE
Value Coding Month
0 0 0 0 0 Reserved
1 0 0 0 1 January




12 1 1 0 0 December
13 - 15 1 1 0 1 - 1 1 1 1 Reserved
4.1.4 Day
Table 4-3: Coding Format for the Day IE
Value Coding Day
0 0 0 0 0 0 Reserved
1 0 0 0 0 1 1.




31 1 1 1 1 1 31.
4.1.5 Hour
Table 4-4: Coding Format for the Hour IE
Value Coding Hour
0 0 0 0 0 0 0
1 0 0 0 0 1 1




23 1 0 1 1 1 23
24 - 31 1 1 0 0 0 - 1 1 1 1 1 Reserved
4.1.6 Minute
Table 4-5: Coding Format for the Minute IE
Value Coding Minute
0 0 0 0 0 0 0 0
1 0 0 0 0 0 1 1




59 1 1 1 1 0 0 59
60 - 63 1 1 1 1 0 1 - 1 1 1 1 1 1 Reserved
4.1.7 Second
Table 4-6: Coding Format for the Second IE
Value Coding Minute
0 0 0 0 0 0 0 0
1 0 0 0 0 0 1 1




59 1 1 1 1 0 0 59
60 - 63 1 1 1 1 0 1 - 1 1 1 1 1 1 Reserved
5. Area and Location Coding
5.1 General Format
Area coding used to define some specific geographical positions, areas etc. For TTI, several distinct
formats are used to describe locations, depending on the nature of the location and system requirements.
For this reason a location reference always consists of two parts:
a location type IE, which defines the method of coding and
a location IE, which contains the information coded according to the corresponding location type.
The definition of bit order is given in ENV 14821-1.
Four different location types are distinguished according to Table 5-1.
Table 5-1: Defined values for Location Type
Value Code Location Type
00 0 ILOC
10 1
WGS 84 (low resolution: » 50 m)
21 0
WGS 84 (high resolution » 1 m)
31 1
TMC-Location
For each of the four location types there is an appropriate definition for the location field.
5.2 WGS 84
The location coding is done by means of WGS84 coordinates (latitude, longitude) to define points.
Additionally length parameter and angles may occur.
A number of different shapes are defined to allow for flexible location referencing. They are distinguished by
the area type identifier as first IE of each element. The following shapes are defined:
Table 5-2: Definition of Area Types
Shape Area Type
Point (latitude, longitude) 0 0 0 0
Circle 0 0 0 1
Ellipse 0 0 1 0
Square 0 0 1 1
Rectangle 0 1 0 0
Polygon / Polygonal Line 0 1 0 1
Corridor 0 1 1 0
Sector 0 1 1 1
reserved 1000 - 1111
The formats for low and high resolution differ only in the word lengths of latitude and longitude. Therefore
the coding is described for both resolutions together.
5.2.1 Parameter Coding
5.2.1.1 Coordinates for Low Resolution

Only WGS84-coordinates are given in TTI messages.
The Longitude may vary in the range -180° … +180°. 0° corresponds to the Greenwich Meridian. Positive
numbers correspond to east, negative numbers to west longitude.
The Latitude may vary in the range -90° … +90°. -90° corresponds to the south pole, 0° to the equator and
+90° to the north pole.
-11
The coordinates are transmitted as binary numbers (2-complement) in units of 2 degrees, which
corresponds to approximately 54 m in north direction. The resolution in longitude is approximately 54 m at
the equator, 46 m at 30° latitude (central europe) and 18 m at 70° latitude. The field width is 20 bits for each
coordinate.
5.2.1.2 Coordinates for High Resolution
Only geographical WGS84-coordinates are given in TTI messages.
The Longitude may vary in the range -180° … +180°. 0° corresponds to the Greenwich Meridian. Positive
numbers correspond to east, negative numbers to west longitude.
The Latitude may vary in the range -90° … +90°. -90° corresponds to the south pole, 0° to the equator and
+90° to the north pole.
-17
The coordinates are transmitted as binary numbers (2-complement) in units of 2 degrees which
corresponds to approximately 0.85 m in north direction. The field width is 26 bit for each coordinate.
5.2.1.3 Length Parameter
All width parameters are given in metres. The coding is in binomial form (see 13) with parameters
C = 10 m
x = 01.
The transmitted value N is coded in 7 bits (0 £ N £ 127). This results in a range of possible lengths between
1 m and 1807 km. (N=0 leads to l=0, which may lead to a degradation of geometrical shapes)
5.2.1.4 Angles
Angles are given in degrees with a resolution of 1°. The range is 0° … 360° leading to a field width of 9 bit.
The coding is done as an unsigned integer (binary number). The angles are measured in clockwise
direction.
5.2.2 Definition of Shapes
5.2.2.1 Point
A point is described by the two coordinates (WGS 84: latitude and longitude). The coding of the location is
summarized in Table 5-3.
Table 5-3: Coding of Location IE in case of a point (WGS84-Position)
Information Element Type Length (bits) for Length (bits) for
Low Resolution High Resolution
Area Type MF 4 4
Longitude MF 20 26
Latitude MF 20 26
The coding of latitude and longitude is performed according to 5.2.1.1 resp. 5.2.1.2.
5.2.2.2 Circle
A circle is defined by the geographical coordinates of its center (WGS 84) and the radius (half-diameter =
d/2) as illustrated in Figure 5-1.
Figure 5-1 : A circle described by its centre and radius
d/2
The coding of the location is summarized in Table 5-4.
Table 5-4: Coding of Location IE in case of a circle
Information Element Type Length (bits) for Length (bits) for
Low Resolution High Resolution
Area Type MF 4 4
Center: Longitude MF 20 26
Center: Latitude MF 20 26
Radius (d/2) MF 7 7
The coding of latitude and longitude is performed according to 5.2.1.1 resp. 5.2.1.2. The radius IE is coded
according to 5.2.1.3.
5.2.2.3 Ellipse
An ellipse may have arbitrary eccentricity and orientation. It is defined by its center, a major half axis (a), a
minor half axis (b) and the angle between the north direction and the major half axis, see Figure 5-2.
Figure 5-2: Definition of an Elipse
North
j
b
a
The coding of the location is summarized in Table 5-5.
Table 5-5: Coding of Location IE in case of an ellipse
Information Element Type Length (bits) for Length (bits) for
Low Resolution High Resolution
Area Type MF 4 4
Center: Longitude MF 20 26
Center: Latitude MF 20 26
Major Half Axis (a) MF 7 7
Minor Half Axis (b) MF 7 7
Angle between Major Half Axis and MF 9 9
North direction (j)
The coding of latitude and longitude is performed according to 5.2.1.1 resp. 5.2.1.2. The coding for the half
axes is accorcing to 5.2.1.3 and for the angle according to 5.2.1.4.
5.2.2.4 Square
A square is defined by the coordinates of the center and the half width a/2. The sides lay in north-south and
east-west direction as illustrated in Figure 5-3.
Figure 5-3: Definition of a square
w/2
The coding of the location is summarized in Table 5-6.
Table 5-6: Coding of Location IE in case of a square
Information Element Type Length (bits) for Length (bits) for
Low Resolution High Resolution
Area Type MF 4 4
Center: Longitude MF 20 26
Center: Latitude MF 20 26
Half-Width (w/2) MF 7 7
The coding of latitude and longitude is performed according to 5.2.1.1 resp. 5.2.1.2. The coding for the half
axes is accorcing to 5.2.1.3.
5.2.2.5 Rectangle
A rectangle may have an arbitrary orientation. It is defined by its center, a major half axis (a/2), a minor half
axis (b/2) and the angle between the north direction and the major half axis (j), see Figure 5-4.
Figure 5-4: Definition of a rectangle
North
j
a/2
b/2
The coding of the location is summarized in Table 5-7.
Table 5-7: Coding of Location IE in case of a rectangle
Information Element Type Length (bits) for Length (bits) for
Low Resolution High Resolution
Area Type MF 4 4
Center: Longitude MF 20 26
Center: Latitude MF 20 26
Major Half-Side (a/2) MF 7 7
Minor Half-Side (b/2) MF 7 7
Angle between Major Half-Side and MF 9 9
North direction (j)
The coding of latitude and longitude is performed according to 5.2.1.1 resp. 5.2.1.2. The coding for the
half-sides is accorcing to 5.2.1.3 and for the angle according to 5.2.1.4.
5.2.2.6 Polygon / Polygonal Line

A polygon is defined by a series of points. The number of points may vary in the range 1 … 16. The points
are connected in the order they appear in the message.
This shape can be used to describe polygons (closed) as well as a polygonal line (open). They are
distinguished using the Open/Closed-Flag. In case of a polygon the last point is connected to the first one.
For both cases examples are given in Figure 5-5.
C D
B
C
B
D
A
A
Figure 5-5: Definition of a Polygon / Polygonal Line
The coding of the location is summarized in Table 5-8.
Coding of Location IE in case of a Polygon / Polygonal Line
Table 5-8:
Information Element Type Length (bits) for Length (bits) for
Low Resolution High Resolution
Area Type MF 4 4
Open/Closed-Flag MF 1 1
Number of Points MF 4 4
1. Point: Longitude MF 20 26
1. Point: Latitude MF 20 26


Point N: Longitude MF 20 26
Point N: Latitude MF 20 26
The coding of latitude and longitude is performed according to 5.2.1.1 resp. 5.2.1.2.
5.2.2.6.1 Open/Closed--Flag
The flag determines, wether the last point is connected to the first one (polygon) or not (polygonal line).
Table 5-9: Flag Open/Closed
Value Open/Closed-Flag Type of shape
0 Open (polygonal line)
1 Closed (polygon)
5.2.2.6.2 Number of Points
The Number of points is given as a binary number. The maximum value of N=16 is indicated by all zeros.
5.2.2.7 Corridor
A corridor is the area given by the outer shape of several rectangles. The description uses a series of points
and half-widths, as illustrated in Figure 5-6 (in this example points O … O and half-widths w /2 … w /2).
1 4 1 3
The rectangles are connected subsequently, and the intended area is the union of the individual rectangles.
Figure 5-6: Definition of a coridor
The coding of the location is summarized in Table 5-10.
Table 5-10: Coding of Location IE in case of a corridor
Information Element Type Length (bits) for Length (bits) for
Low Resolution High Resolution
Area Type MF 4 4
Number of Points MF 3 3
Longitude Point 1 MF 20 26
Latitude Point 1 MF 20 26
Half-Width 1 MF 7 7


Longitude Point N MF 20 26
Latitude Point N MF 20 26
Half-Width N MF 7 7
5.2.2.7.1 Number of Points
The number of points describing the Corridor may vay from 2 to 9. The number N is calculated from the IE
contents (IE) as
NI=+E 2 .
5.2.2.7.2 Longitude / Latitude
The coding of latitude and longitude is performed according to 5.2.1.1 resp. 5.2.1.2. The coding for the half-
widths is accorcing to 5.2.1.3.
5.2.2.7.3 Half-Width
The half-width is coded with the binomial formula described in 5.2.1.3. The half-width submitted with the
last point has no effect on the shape.
5.2.2.8 Sector
A Sector is defined by the center (WGS 84) the radius, the angle against north direction j and the opening
angle a as illustrated in Figure 5-7.
Figure 5-7 : Definition of a sector
North
a
j
r
The coding of the location is summarized in Table 5-11.
Table 5-11: Coding of Location IE in case of a sector
Information Element Type Length (bits) for Length (bits) for
Low Resolution High Resolution
Area Type MF 4 4
Center: Longitude MF 20 26
Center Latitude MF 20 26
Radius MF 7 7
Direction jMF 9 9
Opening Angle aMF 9 9
The element coding is described in 5.2.1 (center coordinates: 5.2.1.1 and 5.2.1.2, radius: 5.2.1.3 and both
angles: 5.2.1.4).
5.3 ILOC
The method, called ILOC referencing, was developed between September 1995 and October 1997 by the
ERTICO Committee on Location Referencing, following earlier work in the framework of the Socrates
project. The method provides a location referencing scheme that is independent from the map database
and has no need for doing any pre-coding.
An intersection locations (ILOC) exists where two or more roads, having different road descriptors, meet.
The ILOC descriptor consists of the WGS84 co-ordinate pair of the approximate centre of the ILOC (in 10
microdegrees), plus the first five characters of 3 road descriptors, of different road sections connecting at
the ILOC. Main road descriptors are road numbers and road names.
For transmission within the application data protocol layer the coding is as follows:
Table 5-12: Coding Format of the Location IE in case of an ILOC
Information Element Type Length (bits)
Geographical Coordinates MF 52
Road Descriptor 1 MV var.
Road Descriptor 2 MV var.
Road Descriptor 3 MV var.
The coding of the coordinate pair conforms to 5.2.1.2 (WGS 84 with high resolution).
The road descriptors are text elements of up to 5 characters. The coding is done as specified for the data
type Text and Transparent Data. Road descriptors may be empty.
5.4 TMC-Location
TMC-Locations are locations identified by Local Authorities. The format of the location IE with a length of 30
bits is given in Table 5-13.The coding of the four parts is specified within the ALERT C protocol.
Table 5-13: Coding Format of Location IE in case of a TMC-Location
Information Element Type Length (bits)
EBU Country Code MF 4
Database Number MF 6
PLOC MF 16
Extent MF 4
6. Communication Address
6.1 General
Communication addresses submitted in the application data protocol are used to establish communication
with a third party. To allow effective signalling, additional information is given to identify the type of
connection.
If no address is submitted, the IE „Network ID“ is set to „unknown“, the IE „Adress Length“ is set to zero and
the IE „Address is not present.
6.2 Network ID
The Network ID specifies the network the address is related to. Additionally the ID may specify (in some
cases) the communication service, which shall be used to reach the addressee. The following entries are
possible:
Table 6-2: Network ID
Network / Service Value Code
Unknown 0 00000
ISDN Numbering Plan (E.164/E.163): Speech 1 00001
ISDN Numbering Plan (E.164/E.163): Data 2 00010
Cellular Mobile Network: Speech 3 00011
Cellular Mobile Network SMS 4 00100
Cellular Mobile Network BS24 5 00101
Cellular Mobile Network GPRS 6 00110
X.25 7 00111
X.400 (e-mail) 8 01000
Internet (e-mail) 9 01001
reserved 10 01010
TCP/IP 11 01011
UDP/IP 12 01100
FAX Group 2/3 13 01101
FAX Group 4 14 01110
Cellular Mobile Network BS 26 15 01111
Cellular Mobile Network BS 26, UDI 16 10000
Cellular Mobile Network Speech / UUS 17 10001
reserved 18 - 31
6.3 Validity Range of Address
The Validity Range of the Address indicates whether the address is a national or an international one. If this
is unknown the field has to be set to zero.
Table 6-3: Validity Range of Address
Type Value Coding
unknown 0 00
international address 1 01
national address 2 10
reserved 3 11
6.4 Flag BCD/ASCII
The flag specifies whether the characters of the following address are coded BCD or ASCII.
Table 6-4: Flag BCD/ASCII
Value Coding
0BCD
1 ASCII
6.5 Address Length
The IE gives the number of characters submitted in the following address field, coded as a binary number in
the range 0 . 255.
6.6 Address
The address is coded beginning with the first character. If the address length is set to 0, the address field is
not submitted. The Coding of the individual characters depends on the flag BCD/ASCII:
BCD: each character is BCD-coded with 4 bits. Valid characters are the digits 0 . 9 and the
control characters +, *, #. The coding is as follows:
Character Coding (Hex)
digits 0 . 9 0 . 9
+A
*B
#C
ASCII: Each character is coded with 8 bits. The ASCII character set is used. Only values 0 . 127
are valid.
7. Text and Transparent Data
7.1 Format of a Text Element
7.1.1 General
The coding is done with a text representation element, a length identifier and a text (or data) field. The IE´s
„Length“ and „Text / Data“ are optional. If no text is submitted, both IE´s are not present. The definition of bit
order is given in ENV 14821-1.
7.1.2 Text Representation
The text representation determines whether text or transparent data are submitted and in case of text
whether each character is coded in 6 or 8 bits.
If the value is zero, no data will be submitted. In this case there is neither a length IE nor a text field present.
Table 7-3: Values for Text Representation
Value Code Count of bits per character
0 0 0 no data submitted
1 0 1 Text; 6 bits per character
2 1 0 Text ISO 8859-1
(8 bits per character)
3 1 1 transparent data
7.1.3 Length
The length identifier gives the number of characters in the text field - including control characters. In case of
transparent data the length IE specifies the number of bytes. The value is coded as a binary number.
7.1.4 Text
7.1.4.1 General
The text field contains the data. The coding is dependent on the content of the text representation IE as
described below.
7.1.4.2 Text, 8 Bits per Character
As character set the ISO 8859-1 code (version 1987) is used; see 7.1.5.
7.1.4.3 Text, 6 Bits per Character
In order to allow coding of international characters, five character sets are defined (see 7.1.6). The first
character set is used as default and contains upper and lower case letters and some punctuation marks.
60 of totally 64 values of each character set are provided for real characters. Furthermore 5 control
characters (switches) are provided to switch to another character set. Switches immediatly followed by a
real character activate the corresponding character set. Switches following one another may be used for
switching to further character sets. The new character set is valid until the next switch occurs.
Until a switch occurs in the text the values are interpreted as characters of the default character set.
7.1.4.4 Transparent Data
The binary data are submitted with a full number of bytes. If the number of bits cannot be devided by 8, the
last bits of the data field shall be set to zero.
7.1.5 ISO 8859-1 Character Set

The characters 0 - 127 are identical with the ASCII code. The characters 128 - 255 are coded according to
the following table.
Table 7-1 : Coding of 128 - 255
Dec. Dec. Dec.
Hex. Char. Hex. Char. Hex. Char. Dec. Hex. Char.
128 160 192
80 A0 C0 À 224 E0 à
129 161 193
81 A1 ¡ C1 Á 225 E1 á
130 162 194
82 A2 ¢ C2 Â 226 E2 â
131 163 195
83 A3 £ C3 Ã 227 E3 ã
132 164 196
84 A4 ¤ C4 Ä 228 E4 ä
133 165 197
85 A5 ¥ C5 Å 229 E5 å
134 166 198
86 A6 ¦ C6 Æ 230 E6 æ
135 167 199
87 A7 § C7 Ç 231 E7 ç
136 168 200
88 A8 ¨ C8 È 232 E8 è
137 169 201
89 A9 © C9 É 233 E9 é
138 170 202
8A AA ª CA Ê 234 EA ê
139 171 203
8B AB « CB Ë 235 EB ë
140 172 204
8C AC ¬ CC Ì 236 EC ì
141 173 205
8D AD CD Í 237 ED í
142 174 206
8E AE ® CE Î 238 EE î
143 175 207
8F AF ¯ CF Ï 239 EF ï
144 176 208
90 B0 ° D0 Ð 240 F0 ð
145 177 209
91 B1 ± D1 Ñ 241 F1 ñ
146 178 210
92 B2 ² D2 Ò 242 F2 ò
147 179 211
93 B3 ³ D3 Ó 243 F3 ó
148 180 212
94 B4 ´ D4 Ô 244 F4 ô
149 181 213
95 B5 μ D5 Õ 245 F5 õ
150 182 214
96 B6 ¶ D6 Ö 246 F6 ö
151 183 215
97 B7 · D7 × 247 F7 ÷
152 184 216
98 B8 ¸ D8 Ø 248 F8 ø
153 185 217
99 B9 ¹ D9 Ù 249 F9 ù
154 186 218
9A BA º DA Ú 250 FA ú
155 187 219
9B BB » DB Û 251 FB û
156 188 220
9C BC ¼ DC Ü 252 FC ü
157 189 221
9D BD ½ DD Ý 253 FD ý
158 190 222
9E BE ¾ DE Þ 254 FE þ
159 191 223
9F BF ¿ DF ß 255 FF ÿ
Note:  = „Non Breaking Space;  = „Soft Hyphen“
7.1.6 6 Bit Character Set
Table 7-2: 6-Bit Character Set
Dec. Char. Set 1 Char. Set 2 Char. Set 3 Char. Set 4 Char. Set 5
Hex.
⇒ C.S. 1 ⇒ C.S. 1 ⇒ C.S. 1 ⇒ C.S. 1 ⇒ C.S. 1
⇒ C.S. 2 ⇒ C.S. 2 ⇒ C.S. 2 ⇒ C.S. 2 ⇒ C.S. 2
2 ⇒ C.S. 3 ⇒ C.S. 3 ⇒ C.S. 3 ⇒ C.S. 3 ⇒ C.S. 3
3 ⇒ C.S. 4 ⇒ C.S. 4 ⇒ C.S. 4 ⇒ C.S. 4 ⇒ C.S. 4
4 ⇒ C.S. 5 ⇒ C.S. 5 ⇒ C.S. 5 ⇒ C.S. 5 ⇒ C.S. 5
5 a0Àa05
6 b1Áb06
7 c2 Âc06
8 d3Ãd08
9 e4Äe09
10 f5 Åf0A
11 g6Æg0B
12 h7Çh0C
13 i8 Èi0D
14 j9 Éj0E
15 k( Êk0F
16 l) Ël10
17 m[ Ìm11
18 n] Ín12
19 o{ Îo13
20 p} Ïp14
21 q+ Ñq15
22 r Ò-r16
23 s–Ós17
24 t/Ôt18
25 u‚Õu19
26 v? Öv1A
27 w´ ×w1B
28 x` Øx1C
29 y” Ùy1D
30 z“ Úz1E
Dec. Char. Set 1 Char. Set 2 Char. Set 3 Char. Set 4 Char. Set 5
Hex.
31 A; ÛA1F
32 20 B $ ÜB
33 21 C & ÝC
34 22 D ° ßD
35 23 E # àE
36 24 F % áF
37 25 G § âG
38 26 H * ãH
39 26 I ½ äI
40 28 J ¼ åJ
41 29 K ¾ æK
42 2A L « çL
43 2B M » èM
44 2C N | éN
45 2D O - êO
46 2E P : ëP
47 2F Q , ìQ
48 30 R . íR
49 31 S îS
50 32 T ïT
51 33 U ñU
52 34 V òV
53 35 W óW
54 36 X ôX
55 37 Y õY
56 38 Z öZ
57 39 . ø .
58 3A , ù ,
59 3B ú--
60 3C : û :
61 3D ! ü !
62 3E / ý /
63 3F ÿ
8. Extended Location Block
8.1 General
The extended location block (ELB) will be used to locate the vehicle on a digital road map with a low error
probability. It contains information about the last travelled distance: a chain of positions (ELB-waypoints)
including additional information. The ordering is backward in time, i.e. the ELB-waypoint 1 is the actual
position (or the last point, location information was available). At the end of the extended location blockGPS
raw data to one of the chain elements may be transmitted (optional, further investigations for that procedure
might lead to extension to more than one raw data set). The raw data are intended to allow for reverse
DGPS. If this information is submitted, it shall be given for the last ELB-waypoint with good GPS conditions.
The chain is separated in groups: general information, ELB-waypoints 1 to N and GPS raw data as
illustrated in Table 8-1.
Table 8-1: Format of Extended Location Block
Information Element Type Length (Bit) Comment
Number of ELB-Waypoints - 1 MF 4 see 5.1
Time Difference between MF 10 see 8.3
Gene-ration Time and ELB-
Waypoint 1
ELB-Waypoint 1 OF 117 see 8.4
...
ELB-Waypoint N OF 117
Flag GPS Raw Data Present MF 1 see 8.5
GPS Raw Data OV var. see 8.6
8.2 Number of ELB-Waypoints - 1
This field is used as a length identifier. Its value is the number of chain elements minus one (coded as a
binary number), which is the index of the oldest chain element.
8.3 Time Difference between Generation Time and ELB-Waypoint 1
The recording time difference between the last ELB-waypoint and the generation time of the message is
given in seconds as a binary number. The value 1023 indicates Dt ‡ 1023 s.
8.4 ELB-Waypoint X
8.4.1 General
All ELB-waypoints have the same syntax as described in Table 8-2.
Table 8-2: Coding of a ELB-waypoint
Information Element Type Length (Bit) Comment
Position MF 58 see 8.4.2;
coding see document „Area
and Location Coding“
Road Distance MF 12 see 8.4.3
Velocity MF 8 see 8.4.4
Heading MF 9 see 8.4.5
Max. Heading Deviation Clockwise MF 9 see 8.4.6
Max. Heading Deviation Counter MF 9 see 8.4.7
Clockwise
Quality Indicator: Position MF 4 see 8.4.8
Quality Indicator: Road Distance MF 4 see 8.4.9
Quality Indicator: Heading MF 4 see 8.4.10
8.4.2 Position
Position, coded as point with high resolution according to the 5.2.1.2.
8.4.3 Road Distance
Travelled road distance from the previous ELB-waypoint (i.e. the ELB-waypoint with index i+1). The
distance is given in meter as a binary number. For the oldest ELB-waypoint the road distance is
meaningless but shall be set to zero. A value of 4095 indicates a distance Ds ‡ 4095 m.
8.4.4 Velocity
Current velocity in [km/h]. The v
...