SIST EN 15213-2:2013

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Intelligente Transportsysteme - Systeme für das Wiederfinden gestohlener Fahrzeuge - Teil 2: Bestandteile allgemeiner StatusmitteilungenSystèmes de transport intelligents - Systèmes intervenant après un vol pour la récupération des véhicules - Partie 2 : Éléments de message d'état communsIntelligent transport systems - After-theft systems for the recovery of stolen vehicles - Part 2: Common status message elements43.040.15Car informatics. On board computer systems35.200Vmesniška in povezovalna opremaInterface and interconnection equipment13.310Varstvo pred kriminalomProtection against crimeICS:Ta slovenski standard je istoveten z:EN 15213-2:2013SIST EN 15213-2:2013en,fr,de01-september-2013SIST EN 15213-2:2013SLOVENSKI
STANDARDSIST-TS CEN/TS 15213-2:20061DGRPHãþD



SIST EN 15213-2:2013



EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 15213-2
June 2013 ICS 35.240.60 Supersedes CEN/TS 15213-2:2006English Version
Intelligent transport systems - After-theft systems for the recovery of stolen vehicles - Part 2: Common status message elements
Systèmes de transport intelligents - Systèmes intervenant après un vol pour la récupération des véhicules - Partie 2 : Éléments de message d'état communs
Intelligente Transportsysteme - Systeme für das Wiederfinden gestohlener Fahrzeuge - Teil 2: Bestandteile allgemeiner Statusmitteilungen This European Standard was approved by CEN on 26 April 2013.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre:
Avenue Marnix 17,
B-1000 Brussels © 2013 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 15213-2:2013: ESIST EN 15213-2:2013



EN 15213-2:2013 (E) 2 Contents Page Foreword .3 Introduction .4 1 Scope .5 2 Normative references .5 3 Terms and definitions .5 4 Numerical notations .5 5 Symbols and abbreviations .6 6 Requirements .6 7 General rules for data elements .7 8 Data protection  General requirements .9 Annex A (normative)
Data elements . 10 Annex B (normative)
Passing data by other means . 25 Bibliography . 26
SIST EN 15213-2:2013



EN 15213-2:2013 (E) 3 Foreword This document (EN 15213-2:2013) has been prepared by Technical Committee CEN/TC 278 “Road transport and traffic telematics”, the secretariat of which is held by NEN. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by December 2013, and conflicting national standards shall be withdrawn at the latest by December 2013. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights. This document supersedes CEN/TS 15213-2:2006. It is derived from a suite of CEN Technical Specifications CEN/TS 15213-1 to -6 inclusive dealing with the tracking and recovery of stolen vehicles. Parts 1 to 5 inclusive have been upgraded to EN status without change. CEN/TS 15213-6:2011 remains a valid Technical Specification as of the date of this publication and will be considered for EN status in due course. All these documents remain related and should be read in conjunction according to the type of technology, product or service being considered. EN 15213 consists of the following parts:  EN 15213-1, Intelligent transport systems — After-theft systems for the recovery of stolen vehicles — Part 1: Reference architecture and terminology;  EN 15213-2, Intelligent transport systems — After-theft systems for the recovery of stolen vehicles — Part 2: Common status message elements (the present document);  EN 15213-3, Intelligent transport systems — After-theft systems for the recovery of stolen vehicles — Part 3: Interface and system requirements in terms of short range communication system;  EN 15213-4, Intelligent transport systems — After-theft systems for the recovery of stolen vehicles — Part 4: Interface and system requirements in terms of long range communication system;  EN 15213-5, Intelligent transport systems — After-theft systems for the recovery of stolen vehicles — Part 5: Messaging interface;  CEN/TS 15213-6, Road transport and traffic telematics — After-theft services for the recovery of stolen vehicles — Part 6: Test procedures1). According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.
1) Part 6 awaits final evaluation and ratification as EN and until such time remains a valid part of this EN as CEN/TS 15213-6:2011. SIST EN 15213-2:2013



EN 15213-2:2013 (E) 4 Introduction
This European Standard 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 European Standard 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 European Standard refers to the potential development of systems to enable law enforcement agencies to remotely slow and/or stop the engines of stolen vehicles. This situation remains and further information is available in 2012 CEN publication N2643 Feasibility Report on Remote Slow and Stop Technology, available from CEN/TC 278.
This document should be read in conjunction with EN 15213-1 which provides the preliminary framework for ATSVR concepts.
SIST EN 15213-2:2013



EN 15213-2:2013 (E) 5 1 Scope This European Standard 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 EN 15213 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 EN 15213 aims to identify the main elements and illustrate the data concepts and way forward. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 15213-1:2013, Intelligent transport systems  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) 3 Terms and definitions For the purposes of this document, the terms and definitions given in EN 15213-1:2013 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 0111112. SIST EN 15213-2:2013



EN 15213-2:2013 (E) 6 Characters will be encoded in ASCII and represented as follows:  Characters will have no subscript or hyphen:
EXAMPLE ABC59MNO 5 Symbols and abbreviations For the purposes of this document, the symbols and abbreviations given in EN 15213-1:2013 and the following apply. AEI
Automatic Equipment Identification ASCII
American Standard Code for Information Interchange ATSVR
After Theft System for Vehicle Recovery AVI
Automatic Vehicle Identification RTTT
Road Traffic and Transport Telematics 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; SIST EN 15213-2:2013



EN 15213-2:2013 (E) 7  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 Sector Identifier Length RTTT Application Identifier Length Coding structure Identifier Length CS Data Field
EXAMPLE 1 For a data content field of 6 bytes or octets: RTTT sector Identifier
(to be found)
nm16 Length, number of bytes following this length field e.g. 11
0B16 RTTT Application Identifier
(to be found)
pq16 Length, number of bytes following this length field e.g. 09
0916 Coding structure Identifier e.g. 1
4116 Length, number of bytes following this length field e.g. 07
0716 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. 110F16 Unique number 32 bits e.g. 1234567816 Total
56 bits or 7 bytes 7 General rules for data elements 7.1 General points This subclause 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. SIST EN 15213-2:2013



EN 15213-2:2013 (E) 8 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/country_codes.htm. 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 116 latinAlphabetNo2 2 216 latinAlphabetNo3 3 316 latinAlphabetNo4 4 416 latincyrillicAlphabet 5 516 latinArabicAlphabet 6 616 latinGreecAlphabet 7 716 latinHebrewAlphabet 8 816 latinAlphabetNo5 9 916 latinAlphabetNo6 10 A16 two OctetBMP 128 8016 fourOctetCanonical 129 8116 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 20011206 for the 6th of December 2001. 7.5 Time Time will default to UTC and be of twelve octets coded as ASCII characters. This format allows sorting by date. The Time data element requires time zone information. YYYYMMDDhhmm EXAMPLE 200112060958 for 09:58 on the 6th of December 2001. SIST EN 15213-2:2013



EN 15213-2:2013 (E) 9 7.6 Time zone The time zone will be represented by the hours difference from UTC. The first octet will be the sign “+” or “-“ and the second and third will be the hours difference.
SZZ EXAMPLE +01 for winter time in Europe. 7.7 String delimiters The standard delimiters of “null” 0016 or <> or <> will be used. 8 Data protection  General requirements All data shall be accurate, up to date and secure, particularly where this relates to personal data. All data shall be kept in accordance with the data protection principles set out by the Council of Europe Convention on 28th January 1981 and shall take account of Recommendation R(87)15 of the Committee of Ministers of the Council of Europe 17th September 1987 concerning the use of personal data in the police sector. There are some variations in requirements across EU member states. Therefore, the data shall also be kept in accordance with the national data protection requirements of the country where the data originates and the country where the data is stored. SIST EN 15213-2:2013



EN 15213-2:2013 (E) 10 Annex A (normative)
Data elements A.1 List of data elements All the messages considered to be part of the common message set will consist of a number of the following message elements. Table A.1 — List of data elements Element Description from heading
CSI Code16 Document Reference Date
01 A.2 Date and time
02 A.3 Dynamic Data, Descriptive Location
11 A.4 Dynamic Data, Direction
12 A.5 Dynamic Data, Geographic Location
13 A.6 Dynamic Data, Speed
14 A.7 Incident, LEA holding original report
20 A.8 Incident, Place of Theft
21 A.14 Incident, Report
22 A.9 Incident, Reporting Person
23 A.10 Incident, Stolen Status
24 A.11 Incident, Theft Update, Location
25 A.13 Incident, Time of Theft
26 A.12 Incident, Unique Reference Number
27 A.15 Incident, vehicle load
28 A.34 Incident, vehicle reference
2A A.36 LEA, Communication
30 A.16 LEA, Identifier
31 A.17 Message Reference
32 A.18 Name and Address, Keeper
33 A.19 Name & Address, Owner
34 A.20 SOC, Communication Number
35 A.21 SOC, Identifier
36 A.22 Message Time
37 A.37 Vehicle, ATSVR Details
48 A.23 Vehicle, Body Type
49 A.24 Vehicle, Colour
50 A.25 Vehicle, Engine Number
47 A.26 Vehicle, Engine Size
41 A.27 Vehicle, Manufacturer
42 A.28 Vehicle, Model
43 A.29 Vehicle, Nationality and Licence Plate
44 A.30 Vehicle, Other Descriptive Information
51 A.31 Vehicle, date of manufacture
52 A.37 Vehicle, Registration Date
46 A.32 Vehicle, VIN
45 A.33 SIST EN 15213-2:2013



EN 15213-2:2013 (E) 11 A.2 Date A.2.1 Function The basic date field is used for defining non-time critical time and data information, such as date of first vehicle registration. This is distinct from the time and date of the message. A.2.2 Coding format Code Data element size Time Zone Time 0116 0F16 3 octets 12 octets A.3 Date and time A.3.1 Function All dynamic data shall be referenced to a specific date and time at which the data was true. This is distinct from the time and date of the message. A.3.2 Coding format Code Data element size Time Zone Time 0216 0F16 3 octets 12 octets A.4 Dynamic Data, Descriptive Location A.4.1 Function The function of this field is to describe a location by reference to visual landmarks apparent to an observer at that location. It may include reference to road numbers allocated by Government e.g. A1234. It may include distances from landmarks. The text description will be in ASCII characters. A road Intersection is regarded as two road descriptors. A relative position is regarded as range and bearing to a Geographic Location. If required, because of the complexity of describing a location or route, more than one dynamic data, descriptive location, elements can be included in one message. A.4.2 Coding format Code Data element size Alphabet Code Text Description 1116 1 octet 1 octet Variable A.5 Dynamic Data, Direction A.5.1 Function The function of this field is to give the direction of movement of a vehicle. Care shall be exercised to distinguish between known direction and unknown direction. A.5.2 Coding structure Code Data element size Descriptor Direction value 1216 0216 or 0416 1 octet 1 octet or 3 octets
SIST EN 15213-2:2013



EN 15213-2:2013 (E) 12 Direction descriptor will be: Description Code Direction not known 0016 Bearing in degrees 0116 8-point compass 0216 Future s
...