CEN/TS 15213-2:2006

SLOVENSKI STANDARD
01-julij-2006
&HVWQDWUDQVSRUWQDLQSURPHWQDWHOHPDWLND6LVWHPL]DRGNULYDQMHXNUDGHQLK
YR]LO±GHO(OHPHQWLVSORãQHJDSRURþLODRVWDQMX
Road transport and traffic telematics - After-theft systems for the recovery of stolen
vehicles - Part 2: Common status message elements
Straßenverkehrstelematik - Systeme zum Wiederauffinden gestohlener Fahrzeuge - Teil
2: Bestandteile allgemeiner Statusmitteilungen
Application télématique pour le transport routier et la circulation - Systemes intervenant
apres un vol pour la récupération des véhicules volés - Partie 2: Eléments de messages
d'état communs
Ta slovenski standard je istoveten z: CEN/TS 15213-2:2006
ICS:
13.310 Varstvo pred kriminalom Protection against crime
35.200 Vmesniška in povezovalna Interface and interconnection
oprema equipment
43.040.15 $YWRPRELOVNDLQIRUPDWLND Car informatics. On board
9JUDMHQLUDþXQDOQLãNLVLVWHPL computer systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

TECHNICAL SPECIFICATION
CEN/TS 15213-2
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
May 2006
ICS 35.240.60
English Version
Road transport and traffic telematics - After-theft systems for the
recovery of stolen vehicles - Part 2: Common status message
elements
Application télématique pour le transport routier et la
circulation - Systèmes intervenant après un vol pour la
récupération des véhicules volés - Partie 2: Eléments de
messages d'état communs
This Technical Specification (CEN/TS) was approved by CEN on 6 September 2005 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
promptly at national level in an appropriate form. 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, Cyprus, Czech Republic, Denmark, Estonia, Finland, France,
Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania,
Slovakia, Slovenia, 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
© 2006 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 15213-2:2006: E
worldwide for CEN national Members.

Contents Page
Foreword.3
Introduction .4
1 Scope .5
2 Normative references .5
3 Terms and definitions .5
4 Numerical notations .5
5 Abbreviations.6
6 Requirements.6
7 General rules for data elements.8
8 Data protection.10
Annex A (normative)  Data elements .11
Annex B (normative) Passing data by other means.26
Bibliography .27

Foreword
This document (CEN/TS 15213-2:2006) has been prepared by Technical Committee CEN/TC 278 “Road
transport and traffic telematics”, the secretariat of which is held by NEN.
CEN/TS 15213 “Road transport and traffic telematics — After-theft systems for the recovery of stolen
vehicles” consists of the following parts:
Part 1: Reference architecture and terminology
Part 2: Common status message elements
Part 3: Interface and system requirements in terms of short range communication system
Part 4: Interface and system requirements in terms of long range communication system
Part 5: Messaging interface
Part 6: Test procedures
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to announce this CEN Technical Specification: Austria, Belgium, Cyprus, Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden,
Switzerland and United Kingdom.
Introduction
This document was developed by CEN/TC 278 "Road transport and traffic telematics" Working Group 14
(WG 14) on the subject of After Theft Systems for Vehicle Recovery (ATSVR).
WG 14 comprised representatives and experts from police, insurance associations (CEA), car manufacturers,
transport associations, vehicle rental associations and ATSVR system and product providers. The work was
also in cooperation with Europol and the European Police Cooperation Working Group (EPCWG).
This document was developed to define an architecture within guidelines from CEN/TC 278 through which a
level of interoperability can be achieved between Systems Operating Centres (SOC) and Law Enforcement
Agencies (LEA), both nationally and internationally.
This will provide minimum standards of information and assurance to users as to the functionality of systems,
thereby enabling the recovery of vehicles, detection of offenders and a reduction in crime.
This document should be read in conjunction with CEN/TS 15213-1 which provides the preliminary framework
for ATSVR concepts.
1 Scope
This document specifies the basic structure of the message elements, or items of information, that are put
together to form the common message sets used in exchanging information in an After Theft System for
Vehicle Recovery.
Parts 3, 4 and 5 of CEN/TS 15213 will define the content of these messages. The design is such that all
currently identified information can be included in an unambiguous format, while allowing for additional items
to be included should they either be required in the future or become available in the future.
These message elements can also be referenced in a unique manner and described in plain language for
transmission by voice, fax or e-mail. Similarly the data can be encoded in XML language for electronic
transmission.
Standards for Automatic Vehicle Identification (AVI) and Automatic Equipment Identification (AEI) are being
developed by CEN/TC 278 WG 12 in parallel with EN ISO 14814. This ATSVR standard does not prejudice
that work and does not seek to establish parameters for future AVI/AEI standards. DSRC and AVI standards
are seen as the basic technology blocks for types of short-range ATSVR systems.
This part of CEN/TS 15213 aims to identify the main elements and illustrate the data concepts and way
forward.
2 Normative references
The following referenced documents are indispensable for the application 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.
CEN/TS 15213-1:2005, Road transport and traffic telematics – After-theft systems for the recovery of stolen
vehicles – Part 1: Reference architecture and terminology
EN ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country
codes (ISO 3166-1:1997)
3 Terms and definitions
For the purposes of this document, the terms and definitions given in CEN/TS 15213-1:2005 apply.
4 Numerical notations
Numerical notations are represented as follows:
 Decimal (“normal”) notation will have no subscript
EXAMPLE 127
 Hexadecimal numbers will be denoted by the subscript 16
EXAMPLE 7F16
 Binary numbers will be denoted by the subscript 2
EXAMPLE 011111
Characters will be encoded in ASCII and represented as follows:
 Characters will have no subscript or hyphen
EXAMPLE ABC59MNO
5 Abbreviations
5.1
AEI
Automatic Equipment Identification
5.2
ASCII
American Standard Code for Information Interchange
5.3
ATSVR
After Theft System for Vehicle Recovery
5.4
AVI
Automatic Vehicle Identification
5.5
RTTT
Road Traffic and Transport Telematics
See also CEN/TS 15213-1.
6 Requirements
6.1 General requirements
The coding structure defined in this document is an enabling structure. It is designed to allow combinations of
data elements to be used in composite data structures. It is designed to allow as much interoperability of the
data elements as possible. Data elements may be of any length and may be combined in many ways.
This document recognises that there will be systems of different capability that should be interoperable, even
though the systems may be significantly different. Even where information is obtained by a proprietary system,
the data, once collected, is held in a common interoperable format and so may be accurately and confidently
used.
The document has been designed according to the principles of ISO/IEC 8825-2. The encoding rules enable
the chaining of multiple data elements to build complex data structures
The structure is built from a series of data elements that identify:
a) First the Sector Identifier indicating that it is an RTTT data structure.
b) Second the RTTT Application Identifier.
c) Third the Coding structure Identifier.
d) Fourth (et seq.) the data elements.
By adopting this document, some degree of compatibility can be achieved with AVI and AEI existing standards.
The overall coding structure shall:
 be unambiguous and flexible enough to include relevant numbering structures;
 follow relevant standards;
 provide an exact coding of the data elements;
 be extendable to enable future expansion;
 be able to accommodate private structures.
6.2 Data structure
This subclause refers to a future general ASN.1 coding structure standard being developed by CEN/TC 278.
When this document is available, this subclause will be replaced.
The schematic of the ASN.1 Message is:
RTTT RTTT Coding
CS Data
Sector Length Application Length structure Length
Field
Identifier Identifier Identifier

EXAMPLE 1 For a data content field of 6 bytes or octets
RTTT sector Identifier (to be found)   nm
Length, number of bytes following this length field e.g. 11 0B16
RTTT Application Identifier (to be found)   pq
Length, number of bytes following this length field e.g. 09 09
Coding structure Identifier e.g. 1    41
Length, number of bytes following this length field e.g. 07 07
Data content – 7 bytes
The length field defines the length of the rest of the message, excluding the length field itself.
In the example below the data contents have three data elements: country code, issuer and unique number.
NOTE Each element does not have to be a multiple of 8 bits, although the Data content is a multiple of 8 bits.
EXAMPLE 2 Country code  2 octets e.g. GB
Issuer  14 bits e.g. 110F
Unique number 32 bits e.g. 12345678
Total  56 bits or 7 bytes.
7 General rules for data elements
7.1 General points
This section defines some general codes and rules used by the data elements section, these codes and rules
have been constructed from existing standards where available. Each of the data elements will be given a
unique reference.
7.2 Country code
Country code values shall be assigned according to EN ISO 3166-1.
NOTE An updated list of country codes can be found at
http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/index.html .
7.3 Alphabet Indicator
This is the alphabet used in the rest of the message or until another alphabet indicator is read. This is
referenced in EN ISO 14816.
Definition Decimal Code Hex Code
latinAlphabetNo1 1 1
latinAlphabetNo2 2 2
latinAlphabetNo3 3 3
latinAlphabetNo4 4 4
latincyrillicAlphabet 5 5
latinArabicAlphabet 6 6
latinGreecAlphabet 7 7
latinHebrewAlphabet 8 8
latinAlphabetNo5 9 9
latinAlphabetNo6 10 A
two OctetBMP 128 80
fourOctetCanonical 129 81
Default latinAlphabetNo1
7.4 Date
The date element will be fixed format of eight octets of numbers coded as ASCII characters. It may require a
time zone parameter when used, depending on context.
YYYYMMDD
EXAMPLE 200
...