ISO 14815:2005

Road transport and traffic telematics - Automatic vehicle and equipment identification - System specifications

ISO 14815:2005 defines a generic Automatic Vehicle Identification/Automatic Equipment Identification (AVI/AEI) System specification for nominal AVI/AEI to provide an enabling International Standard, which, whilst allowing the system specifier to determine the performance levels and operating conditions, provides a framework for nominal interoperability.

Télématique du transport routier et de la circulation routière — Identification automatique des véhicules et des équipements — Spécification des systèmes

General Information

• Status: Published
• Publication Date: 14-Jul-2005
• ICS: 03.220.20 - Road transport
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204 - Intelligent transport systems
• Current Stage: 9060 - Close of review
• Completion Date: 02-Sep-2028

Relations

• Consolidates: ISO 14043:2000 - Environmental management - Life cycle assessment - Life cycle interpretation
• Effective Date: 06-Jun-2022
• Revises: ISO/TS 14815:2000 - Road transport and traffic telematics - Automatic vehicle and equipment identification - System specifications
• Effective Date: 15-Apr-2008

Overview

ISO 14815:2005 - Road transport and traffic telematics - Automatic vehicle and equipment identification - System specifications - provides a generic system specification for Automatic Vehicle Identification (AVI) and Automatic Equipment Identification (AEI) in the road transport domain. The standard defines a framework for nominal interoperability (particularly over a DSRC link), allowing system specifiers to select performance classes and operating conditions while ensuring compatible identification between On‑Board Equipment (OBE) and Fixed Equipment (FE).

Key Topics and Requirements

• Scope and core components
  • Defines core elements required for AVI/AEI: a communication link (e.g., DSRC), a reference architecture, common data structures, and operating/environmental parameter classes.
• Architecture and operation
  • Supports both stand‑alone AVI/AEI systems and AVI/AEI as a function within other RTTT/TICS systems.
  • Describes physical architecture and transaction semantics (e.g., successful AVI/AEI transaction, shadowing concepts).
• Data structures and encoding
  • Recommends use of ASN.1 Packed Encoding Rules (PER) for data structure elements to maximize interoperability.
• Performance classes and categories
  • Provides classes and categories to specify environmental and operational requirements (e.g., “ruggedized” vs. “standard”), enabling trade‑offs between cost and performance.
• Air interface and operating parameters
  • Addresses air‑interface aspects and detailed operational parameters that influence successful read transactions.
• Test, compliance and certification
  • Specifies test requirements and classification procedures for components; suppliers must declare classification for each physically separated component to claim compliance.
• Non‑technical considerations
  • Discusses privacy and anonymity topics in the context of related documents (not handled directly in this standard).
• Safety, environmental and marking
  • Includes normative annexes on environmental test parameters, safety, marking of equipment, and compliance procedures.

Applications

• Designing interoperable vehicle/equipment identification systems for tolling, access control, fleet management, enforcement, and traffic data collection.
• Specifying requirements for DSRC‑based identification deployments where cross‑border or multi‑operator nominal interoperability is required.
• Defining component classification and test plans for manufacturers and integrators of OBE and FE.

Who should use this standard

• ITS/RTTT system specifiers and architects
• Transportation authorities and tolling agencies
• OBE and FE manufacturers and integrators
• Test labs, accredited independent testing bodies, and certification organizations
• Consultants and system integrators working on DSRC and vehicle identification systems

Related Standards

• ISO 14816 - Numbering and data structure for AVI/AEI (privacy issues)
• ISO/TR 14814 - Reference architecture and terminology
• ISO/IEC 8825‑2 - ASN.1 PER encoding rules
• ENV 12795 - DSRC Data Link Layer (medium access / LLC)
• ISO 7637 and IEC environmental/EMC standards referenced for testing

Keywords: ISO 14815, Automatic Vehicle Identification, AVI, AEI, DSRC, telematics, system specification, interoperability, ASN.1 PER, OBE, FE.

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 14815
First edition
2005-07-15
Road transport and traffic telematics —
Automatic vehicle and equipment
identification — System specifications
Télématique de la circulation et du transport routier — Identification
automatique des véhicules et équipements — Spécification des
systèmes
Reference number
©
ISO 2005
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 2005
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 2005 – All rights reserved

Contents Page
Foreword. iv
Introduction . v
1 Scope . 1
2 Normative references . 2
3 Compliance. 2
4 Terms and definitions. 2
5 Abbreviations . 4
6 Requirements . 5
6.1 Generic system specification for AVI/AEI systems. 5
6.2 System specification: architecture . 6
6.3 Specific system specification for stand-alone AVI/AEI systems. 8
6.4 Specific system specification for the AVI/AEI system function incorporated into other
systems. 9
6.5 Air interface aspects. 9
6.6 Operating parameters. 9
6.7 Data structure requirements. 13
6.8 Privacy . 13
6.9 Information security . 13
6.10 Environmental parameters . 13
6.11 Safety . 14
7 Test requirements. 14
7.1 Objectives. 14
7.2 Operational parameters to be tested . 14
Annex A (normative) Categories of AVI/AEI systems . 17
Annex B (normative) Environmental parameters to be tested . 22
Annex C (normative) Compliance/certification . 27
Annex D (normative) Safety . 30
Annex E (normative) Marking of AVI/AEI equipment. 31

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 14815 was prepared by the European Committee for Standardization (CEN) Technical Committee
CEN/TC 278, Road transport and traffic telematics, in collaboration with Technical Committee ISO/TC 204,
Intelligent transport systems, in accordance with the Agreement on technical cooperation between ISO and
CEN (Vienna Agreement).
This first edition cancels and replaces ISO/TS 14815:2000, which has been technically revised.
iv © ISO 2005 – All rights reserved

Introduction
System specification
This International Standard is designed to enable users and suppliers of AVI/AEI systems to specify system
specification that will enable a nominal interoperability based on a DSRC link.
The terms “AVI” and “AEI” are used both to describe “independently functioning AVI/AEI systems” and as “the
function of identification within other RTTT/TICS systems”. This International Standard supports both such
uses where no other application or sector standard applies.
Whilst it may be desirable to determine a single set of requirements for operation in all environments and
under all operating conditions, this could impose unacceptable costs.
This International Standard therefore provides standard “classes” for different aspects of system specification,
such that a system specifier may select the appropriate performance parameters to meet a particular
requirement. Supporting informative annexes also provide a number of general use “categories” which may be
used to specify the environmental and operating parameters to support interoperable applications.
The architecture descriptions provided in this International Standard are in compliance with the guidelines
provided by CEN/TC 278 WG13 ISO/TC 204 WG1.
For the data structure elements, Abstract Syntax Notation One (ASN.1) Packed Encoding Rules (PER)
(ISO 8825-2) are used. This usage provides maximum interoperability and conformance to existing standards.
For detailed information on the use of ASN.1 PER for AVI/AEI applications, reference is made to ISO 14816.
This International Standard provides classification procedures and details test requirements needed to support
system definition. These requirements are, wherever possible, determined by reference to existing standards
and established practices.
Test requirements
Test requirements are determined for AVI/AEI system components. The requirements to meet this
International Standard encompass general performance measurement, operational, and environmental
aspects.
How to use this International Standard
It is also an objective to provide users with different applications and in different environmental circumstances
a useful tool that is flexible enough to serve the various different needs. The categorization and classification
system in this International Standard provides for this.
A brief guide showing how to use this International Standard is provided at the end of Annex A.

INTERNATIONAL STANDARD ISO 14815:2005(E)

Road transport and traffic telematics — Automatic vehicle and
equipment identification — System specifications
1 Scope
This International Standard defines a generic AVI/AEI System specification for nominal AVI/AEI to provide an
enabling International Standard, which, whilst allowing the system specifier to determine the performance
levels and operating conditions, provides a framework for nominal interoperability.
Within the road context of the Transport and Traffic Telematics Sector, AVI and AEI systems have the specific
objective of achieving a unique or unambiguous positive identification of a vehicle or item of equipment, and to
make that identification automatically.
Whilst AVI may also be seen as an essential component of some applications, the particular needs of such
systems are outside the scope of this International Standard. As far as is possible, care is still taken to provide
a useful tool for such applications.
This International Standard only refers to AVI/AEI in the road environment. Multimodal and intermodal
exchanges of AVI/AEI are outside the scope of this International Standard.
Where AVI/AEI applications are part of a larger system, and where no standardized application-specific test
requirements exist, these test requirements apply.
Anonymity and privacy issues are discussed in ISO 14816, and are not handled in this International Standard.
This International Standard is designed for system specification that will enable a nominal interoperability
based on a DSRC link. AVI/AEI systems that are relying on other link types are outside the scope of this
International Standard for those parameters where the link type influences parameters.
The scope of this International Standard is confined to generic AVI/AEI system specification for systems that
have the following “core” components:
 A means of communication between the vehicle/equipment and the reading station (e.g. a DSRC link);
 operation within a reference architecture which enables compatible systems to read and interpret the
identification (See ISO TR 14814);
 compliance to commonly understood data structures that enable meaningful interpretation of the data
exchanged in the identification sequence (See ISO 14816);
 the provision of operating and environmental parameters (or classes of operating parameters) within
which such systems must successfully function without impairing interoperability. This is to ensure that
the system specifier can state his requirements clearly to Implementation Designers and Integrators, and
measure the performance of such systems (covered in this International Standard).
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.
ISO 7637-1:1990, Road vehicles — Electrical disturbance by conduction and coupling — Part 1: Passenger
cars and light commercial vehicles with nominal 12 V supply voltage — Electrical transient conduction along
supply lines only
ISO/IEC 8825-2, Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules
(PER) — Part 2
1)
ISO/TR 14814 , Road transport and traffic telematics — Automatic vehicle and equipment identification —
Reference architecture and terminology
1)
ISO 14816 , Road transport and traffic telematics — Automatic vehicle and equipment identification —
Numbering and data structure
ENV 12795, Road Transport and Traffic Telematics (RTTT) — Dedicated Short-Range Communication
(DSRC) — DSRC Data Link Layer: Medium Access and Logical Link Control
IEC 68-1:1987, Basic Environmental Testing Procedures — Part 1: General and Guidance
IEC 68-4:1987, Environmental testing — Part 4: Information for specification writers — Test summaries
IEC 215:1987, Safety requirements for radio transmitting equipment (EN 60215)
IEC 721-3-4:1988, Classification of environmental conditions — Part 3: Classification of groups of
environmental parameters and their severities — Stationary use at non-weather protected locations
IEC 721-3-5:1988, Classification of environmental conditions — Part 3: Classification of groups of
environmental parameters and their severities — Ground vehicle installations
IEC 801-2:1984, Electromagnetic compatibility for industrial-process measurement and control equipment
IEC 1000-4-6, Electromagnetic compatibility (EMC) — Part 4: Testing and measuring techniques — Section 6:
Immunity to conducted disturbances, induced by radio-frequency fields
CEPT/ERC T/R 22/04:1991, Harmonisation of Frequency Bands for Road Transport Information Systems
3 Compliance
In order to claim compliance with this International Standard, a supplier shall provide, for each physically
separated component, detail of the classification of its product for all relevant (environmental and operational)
parameters determined within this International Standard.
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply:
4.1
AVI/AEI system
AVI/AEI application in an RTTT system, either as a stand-alone system or as part of an RTTT application

1) To be published.
2 © ISO 2005 – All rights reserved

4.2
bi-directional monologue
“read only” functionality with a start signal from the FE side
4.3
category
groupings of common class requirements to support interoperability between AVI/AEI systems of common
purpose (e.g. a “ruggedized” category versus a “standard” category)
4.4
class
differentiation between system components with different “grades” of requirements for parameters
(e.g. class 1 for “extreme” operational and environmental requirements)
4.5
environmental parameters
describe different environmental component properties/specifications
4.6
extreme
refers to class 1 requirements for the “ruggedized” system category “A”
4.7
Fixed Equipment (FE)
equipment required to interrogate, receive and interpret the data in the On-Board Equipment (OBE) in order to
present the identification
4.8
lifetime
period of time during which an item of equipment exists and functions according to the relevant requirements
of this International Standard
4.9
maintainability
ability to keep in a condition of good repair or efficiency
4.10
Mean Time to Failure
average time that a system functions before first failure
4.11
Mean Time between Failures
mean cycle (one failure and one repair) time of a maintained system
4.12
Nominal Interoperability
“Application Area Interoperability” in a region spanning two or more areas with cross-border operation
between operator domains, districts or nations, the capability for a nominal AVI/AEI system FE to operate with
a nominal AVI/AEI system OBE
4.13
normal
class 2 requirements for the “standard” system category “B”
4.14
On-Board Equipment (OBE)
equipment fitted to the vehicle or item to be identified and containing the unique or unambiguous positive
identification
4.15
operational parameters
different operational component properties/specifications
4.16
physical architecture
physical configuration and physical interconnection of equipment to achieve its function (not the equipment
itself)
4.17
selected
class 1-6 requirements for the system categories “3 - 6”
4.18
shadowing
condition where the close proximity of a vehicle/equipment interposed between FE and OBE obscures the
signals, thus preventing a successful AVI/AEI transaction
NOTE The shadowing caused by normal traffic behaviour is taken into account and overcome to provide a successful
transaction. Abnormal shadowing may be caused by large or unusually shaped vehicles/equipment or by vehicles
travelling too closely together.
4.19
(AVI/AEI) transaction
completed cycle of communication (across the air interface at reference point delta) wherein a message
identifying a vehicle or item of equipment is successfully received and understood by the receiver during one
passage through the read zone
NOTE The number of attempts, retries and repeats is not relevant, it is only that one fully completed identification
process communication cycle is successfully completed to the extent that no communications error could be detected.
5 Abbreviations
The following abbreviations are used in this International Standard:
AEI Automatic Equipment Identification
AIB Accredited, Independent, Testing Body
ASN.1 Abstract Syntax Notation One
AVI Automatic Vehicle Identification
CEPT Comité Européenne de Postes et Telecommunication (Fr.)
European Committee for Post and Telecommunication
DSRC Dedicated Short Range Communication
DUT Device Under Test
FE Fixed Equipment
MTBF Mean Time Between Failures
OBE On-Board Equipment
OSI Open Systems Interconnection
RTTT Road Transport and Traffic Telematics (CEN/TC 278)
TICS Transport Information and Control Systems (ISO/TC 204)
4 © ISO 2005 – All rights reserved

The following abbreviations are used to designate the IEC 721 — Environmental classes:
B Biological
C Chemical substances
F Contaminating fluids
K Climatic
M Mechanical
S Mechanical substances
Z Special climatic conditions
6 Requirements
6.1 Generic system specification for AVI/AEI systems
This clause summarizes the generic system specification for AVI/AEI systems in terms of functions supported,
data exchanges, categorization and classification. The requirements defined in this clause:
 provide operation within the reference architecture defined in ISO/TR 14814,
 allocate application data in accordance with ENV ISO 14816, and
 enable nominal interoperability.
To obtain interoperability, it is a requirement that nominal AVI/AEI system FE shall have the capability to
operate with nominal AVI/AEI system OBE, albeit of different capability using an air interface as referenced
in 6.5.
However, the environmental and operating conditions within which such equipment has to function may be
different according to geographical location, traffic operating conditions, etc. This International Standard
provides environmental/operational classes grouped into categories to enable the marketplace to decide the
most appropriate FE for individual fixed locations. This is with the knowledge that, within the
operating/environmental constraints selected, any properly configured standard compliant AVI/AEI system
OBE shall have the capability to be identified by all standard compliant AVI/AEI system FE.
To obtain nominal AVI/AEI system interoperability, it is a requirement that OBEs shall have the capability to
operate with nominal AVI/AEI system FE.
However, the environmental and operating conditions within which on-board equipment has to function may
be different according to geographical location, vehicle or equipment type, OBE location, etc. This
International Standard provides options and environmental/operational classes to enable the marketplace to
select the most appropriate OBE equipment, with the knowledge that, within the operating/environmental
constraints selected, any properly configured standard compliant AVI/AEI system FE shall have the capability
to identify all standard compliant AVI/AEI OBEs passing within its compass.
These generic system specifications provide a migration path to later generations of equipment and to
equipment of greater capability.
In order to enable an AVI/AEI system to operate across wide areas, it is necessary for the system to use the
standardized interfaces architecture and data structures normalized in this family of AVI/AEI European
Standards. As particular system specifications will vary, well-declared and flexible structures are used. It is
important, for example, that AVI/AEI system FE facilities can effectively operate different variants of OBE. The
system specification defined in this International Standard supports the numbering schemes and data
structuring defined in ISO 14816.
6.2 System specification: architecture
It is the Vision of the AVI/AEI system specification International Standard to:
“provide a method (trans-national and interoperable) of automatically identifying a vehicle or item of equipment
using a standard DSRC link.”
Other subsequent standards may determine requirements for AVI/AEI systems working at other air interfaces.
It is the Mission of the AVI/AEI system specification International Standard to:
“Define the functionality, environmental and operating parameters (system specification for AVI/AEI) such that
they may achieve the objectives of the Vision Statement in an Open Systems Environment, enabling
interoperability, whilst retaining the ability for different equipment to coexist.”
According to the operational situation, AVI/AEI systems may be viewed either as a service to support an
application (such as the vehicle identification component in a public transport system or freight management
system), or as an application in itself (for example, the identification of a “probe” vehicle in a traffic
management situation or in an enforcement situation). As such, the AVI/AEI system function may be achieved
using purpose-specific dedicated equipment (such as an AVI/AEI system transponder), or may be achieved
using equipment installed for the application that it supports, or indeed, using existing equipment installed for
another application (such as a freight logistics system utilizing AVI techniques). Such multi-application support
and interoperability will be particularly common in respect of the OBE, although it will also be required in
respect of the FE.
6.2.1 Conceptual architecture
See ISO/TR 14814.
6.2.2 Logical architecture
See ISO/TR 14814.
6.2.3 Functional architecture
See ISO/TR 14814.
6.2.4 Control architecture
See ISO/TR 14814.
6.2.5 Identification principles
This International Standard adheres to the Open Systems Interconnection (OSI) philosophy, i.e. the definition
is concerned with the exchange of information between systems and not the internal functioning of each
individual system component.
In order to cooperate, entities in any OSI layer, other than the lowest layer, communicate by means of the set
of services provided by the next lower OSI layer.
This International Standard references the series of International Standards developed by CEN/TC 278/WG9.
The work of ISO/TC 204, especially WG1/SG3, is taken into account as far as possible, as are other existing
relevant definitions of data elements [such as the “Data elements to be used in surface transport applications
of machine readable cards” (CEN/TC 224/WG11)].
6 © ISO 2005 – All rights reserved

Where the RTTT/TICS system service has to support devices in an interoperable environment, it is essential
that the devices be capable of “upwards migration”, either to accommodate different types of devices in the
emerging specifications, or as new generations of systems are developed.
6.2.6 Information architecture
See ISO/TR 14814 and ISO 14816.
6.2.7 Physical (application) architecture
This clause describes the physical configuration and physical interconnection of equipment to achieve its
function (not the equipment itself).
The physical architecture shall be as defined in 4.5 of ISO/TR 14814.
The following clauses provide a summary of the application architecture.
In the majority of situations, the objective of the AVI/AEI system function is to uniquely identify vehicles or
equipment. In some circumstances, the position may be reversed and it may be for a moving vehicle or
equipment to identify a static or moving object (such as a location identifier, or another moving vehicle or
equipment).
In some cases, it is necessary to protect the identity of a vehicle or equipment for reasons of privacy or
security. In these cases, the AVI/AEI system shall provide an alias or temporary unambiguous identification
that does not necessarily provide the permanent identification of the vehicle or equipment. (It may, for
example, identify a smart card temporarily located in an on-board unit.) Such identifications are supported
within this International Standard.

Figure 1 — Example of physical architecture model
The example in Figure 1 shows one central FE system with a number of local FE systems. Each local system
may have one or multiple FE connections. The example also shows OBE of two different types, without
indication of the exact number of each.
The AVI/AEI system may be a stand-alone function using dedicated equipment, or may be an application
service within a more complex service (such as fee collection, route guidance, fleet management, etc.)
achieved using the equipment provided for that service. The FE used may provide the functions of more than
one service, or indeed the function may be performed by a combination of equipment (such as an interrogator
plus an antenna).
The general application configuration shall be comprised of FE and OBE (OBE), making use of the DSRC to
communicate.
The FE shall utilize an antenna targeted on the identification zone. The FE shall normally, but not necessarily,
be connected to either a local and/or a central computer system.
The OBE shall utilize an antenna located such that it will pass through the identification zone.
As the OBE passes through the Identification Zone, communication shall be effected using a DSRC link
(see 5.5). All AVI/AEI system application-specific data shall be comprised of one or more numbering
scheme(s) determined in ISO 14816, or a “private” class data construct supported within that International
Standard.
The AVI/AEI system identification component specified within this International Standard may be described as
a “bi-directional monologue” — bi-directional in that there shall be a communication phase where contact is
established with the OBE and the OBE responds, a monologue in that the AVE/AEI identification is a data
structure (or group of data structures) sent from the OBE to the FE.
Additional bi-directional data exchanges are permissible (and indeed are essential to support many application
services) but are outside the domain of this International Standard. Other standards for the sector shall
prescribe the form of these data exchanges.
An AVI/AEI system identification, or AVI/AEI system component of a more complex RTTT/TICS identification,
shall only be regarded as a standard-compliant identification if it complies with the system specification
determined in this International Standard. In order to ensure interoperability within the sector, no form of
AVI/AEI system, other than that determined in this International Standard (and in the related International
Standards ISO/TR 14814 and ISO 14816), may claim to be compliant with CEN TC 278 RTTT standards for
AVI/AEI systems or ISO/TC 204 TICS International Standards for AVI/AEI systems.
6.2.8 Deployment (implementation) design
The deployment architecture for AVI/AEI systems is not considered appropriate for standardization.
6.3 Specific system specification for stand-alone AVI/AEI systems
This clause defines the specific data exchange operation to achieve the AVI/AEI transaction.
The AVI/AEI transaction is an essentially simple bi-directional monologue transaction in which the FE requests
the data from the OBE and the OBE provides its data.
The data shall comprise one or more standardized data constructs as defined in ISO 14816.
The transaction shall conform to any relevant CEN or ISO system specification standard for AVI/AEI. The
clause below defines the description method used in describing the specific system specification for an
AVI/AEI transaction.
8 © ISO 2005 – All rights reserved

6.3.1 GET function
The principal function to support access to the AVI/AEI data structures (defined in ISO 14816) is:
GET
NOTE This is the only standardized function required to perform AVI/AEI.
GET is an AVI/AEI system function used to initiate a read operation of AVI/AEI system information, i.e.
AVI/AEI system application data.
Usage: GET (〈ASN.1DataStructureIdentifier〉, Data)
6.3.2 Further (optional) functions
Some AVI/AEI systems may additionally provide further functions. The following functions are not mandatory,
but if present shall conform to the following general form and to the definition as specified in any CEN/ISO
AVI/AEI standard. This function requires a full bi-directional link.
6.3.2.1 SET
SET is an AVI/AEI system function used to put data into the memory of on-board equipment (OBE).
Usage: SET(〈ASN.1 DataStructureIdentifier〉.[DataElementIdentifier], data to be written,[〈location〉]).
6.4 Specific system specification for the AVI/AEI system function incorporated into other
systems
The AVI/AEI system may be used as an identification element within another application (e.g. fleet
management, parking management, etc.).
Where an application requires simply an AVI/AEI system identification transaction, it shall use the method
defined in 6.3. above. In cases where there is an application-defined transaction using a standardized DSRC
interface, this International Standard does not apply.
6.5 Air interface aspects
This International Standard assumes the provision of adequate DSRC interface European Standards provided
by ETSI (EN 300 674) and CEN (EN 12253, 12795, 12834). The provisions and determinations specified
within this International Standard assume a DSRC link at 5,795-5,805 GHz as recommended by
CEPT/ERC 22/04 or other frequencies as may be specified in such ETSI and CEN Standards.
NOTE 1 Whilst many of the system specifications determined in this International Standard may be applicable
regardless of the frequency, it will be necessary to reconsider each of the provisions of this International Standard in
situations where new frequency ranges are to be used. Where appropriate, new standards may need to be developed for
specific frequency ranges.
NOTE 2 For ISO parallel voting, the relevant ITU reference will replace or be added to this clause as soon as available.
6.6 Operating parameters
6.6.1 AVI/AEI system operating parameters
In order to claim compliance, a declaration for all tables and table combinations shall be made. Omission of
declaration of any one table or any table combination in this section shall constitute non-conformance to the
International Standard.
Where speed is claimed, the maximum number of transponders in zone shall be declared; where life of
transponders is claimed, the number of reads per period shall be declared.
6.6.1.1 Reliability, availability, lifetime and maintainability
The operational requirements for reliability, availability, lifetime and maintainability on the AVI/AEI system level
are formulated qualitatively, not quantitatively.
6.6.1.1.1 Reliability
This clause relates to the reliability requirements between reference points alpha and delta determined in
ISO/TR 14814.
In order to be considered reliable, a compliant AVI/AEI system shall deliver a declared maximum of
undetected erroneous identification results under nominal operational conditions at reference point beta.
6.6.1.1.2 Maintainability
The FE shall be designed to facilitate maintenance.
The OBE (excluding exchangeable batteries or external power source) shall not require maintenance.
6.6.1.1.3 Minimum number of identifications per year for the OBE
Table 1 — Identification per year for OBE
Class Identifications per year
A1 20 000
A2 10 000
A3 4 000
A4 2 000
Where an internal battery is used in the OBE, Class A is to be considered in conjunction with Class B below.
In order to claim compliance with a particular “Class A” classification, the OBE shall also meet the claimed
OBE lifetime classification.
6.6.1.1.4 Lifetime of OBE
The minimum lifetime of the OBE shall be as determined in Table 2.
Table 2 — Minimum lifetime of OBE
Class OBE lifetime
B1 15 years
B2 10 years
B3 5 years
B4 3 years
B5 2 years
B6 1 year
B7 6 months
B8 3 months
B9 1 month
10 © ISO 2005 – All rights reserved

In the case of using an exchangeable battery in the OBEs, the lifetime of the battery shall be as determined in
Table 3.
Table 3 — OBE battery lifetime
Class Battery lifetime*
BB1 15 years
BB2 10 years
BB3 5 years
BB4 3 years
BB5 2 years
BB6 1 year
BB7 6 months
BB8 3 months
BB9 1 month
*Based on 500 transactions per month.
6.6.1.1.5 Distance between FE and OBE antennas
Table 4 — Distance between FE and OBE antennas
Class Reading distance test points
C1 20 m
C2 10 m
C3 6 m
C4 3 m
C5 1 m
C6 0,5 m
To achieve Class C1, it shall read at all test point, Class C2, all test points up to 10 m, etc.
Where ETSI Standard I-ETS 300 674 applies, distance shall be measured according to power levels as
defined by ETSI Standard I-ETS 300 674. The power class, where applicable, shall be documented
(e.g. Class C1/1, Class C1/2, etc). Applicable ETSI power classes shall not be exceeded.
6.6.1.2 OBE Installation
The technology adopted for an AVI/AEI system shall not preclude OBEs that can be installed by the user
without any aid from any expert.
Installation is to be effected according to an approved, documented procedure provided by the manufacturer.
When being fitted to a vehicle, the equipment and the whole installation must comply with the provisions relating
to maximum tolerances laid down by the manufacturer's specifications.
The equipment shall be immune to damage caused by the normal handling, connection and disconnection
that are necessary for installation and maintenance activities.
This shall not preclude OBEs which are specifically designed to cease functioning upon removal or tampering.
6.6.1.3 Electromagnetic disturbance
The AVI/AEI system shall be able to perform identifications in an environment with electromagnetic
disturbance in accordance with IEC 801 and EN 50081. For the radio link, part I, ETS 300 674 applies.
6.6.1.4 Emissions
The electric or magnetic fields produced by the AVI/AEI system shall not exceed the levels as specified in
IEC 215 (EN 60215). This clause applies to both FE and OBE. For the radio link, part I, ETS 300 674 applies.
EXAMPLE IEC 215 (EN 60215) requires that the transmitted electric and magnetic fields shall not exceed 200 V/m
or 0,5 A/m, respectively over the frequency range 30 MHz to 30 GHz. This approximately corresponds to a radiation power
2 2
density of 100 W/m (10 mW/cm ) and applies to distance greater than 5 cm from accessible surfaces of the equipment.
NOTE For the ISO parallel voting, the relevant ITU reference will replace or be added to this clause as soon as
available.
6.6.2 AVI/AEI system-specific operating parameters
Due to the variations in size and loading configurations of items of equipment that may be encountered in an
RTTT/TICS environment, references to distance detailed in this clause refer to distances between the OBE
antennas.
The system must be able to operate within the limits as specified in the following tables.
Table 5 — Maximum number of OBE antennas per cubic metre
Class OBEs per m
D1 0,1
D2 1
D3 10
D4 25
D5 50
D6 100 and above
NOTE Depending on the technical solution, there may be a requirement to specify the maximum number of OBEs in
the read zone as a factor of passing speed.
Table 6 — Minimum distance between OBE antennas
Class Clearance between OBEs
E1 1 cm
E2 5 cm
E3 10 cm
E4 25 cm and above
NOTE This will normally reference distance between monolithic OBEs when mounted according to manufacturer's
specification.
12 © ISO 2005 – All rights reserved

Table 7 — Passing speed
Class Speed test point
Km/h m/s
F1 240 66
F2 160 44
F3 120 33
F4 72 20
F5 18 5
F6 9 2.5
F7 3.6 1
To achieve Class F1, it shall read at all test point, Class F2, all test points from 1 m/s up to 66 m/s, etc.
NOTE F5 to F7 are applicable classes for use in low-speed AEI environments such as inventory management, etc.,
but are also used as stop-and-go traffic test points.
6.7 Data structure requirements
The overall requirements for AVI/AEI system data are determined within ISO 14816.
6.8 Privacy
Privacy is not a mandatory requirement for a nominal AVI system (or system service), as its principal objective
is to positively identify vehicles/equipment. See ISO 14816 for further details.
6.9 Information security
Security data at the message level and the security information objects (such as cryptographic checksums)
can optionally be provided by adequate measures, but do not form part of this International Standard. See
ISO 14816 for further details.
6.10 Environmental parameters
This clause is applicable for all parameters of operation, transport and storage
The following abbreviations are used to designate the environmental classes defined in IEC 721:
B Biological
C Chemical substances
F Contaminating fluids
K Climatic
M Mechanical
S Mechanical substances
Z Special climatic conditions
6.10.1 FE environmental parameters
FE environmental parameters are classified in accordance with IEC 721-3-4.
Table 8 — Environmental conditions for the FE
Class Reference Category
G1 IEC 721-3-4 4K4/4Z2/4Z5/4Z8/4B1/4C2/4S3/4M4
G2 IEC 721-3-4 4K3/4Z7/4B1/4C2/4S3/4M4
G3 IEC 721-3-4 4K2/4Z7/4B1/4C2/4S3/4M4
G4 IEC 721-3-4 4K1/4Z7/4B1/4C2/4S3/4M4
6.10.2 OBE environmental parameters
OBE environmental parameters are classified in accordance with IEC 721-3-5.
Table 9 — Environmental conditions for the OBE
Class Reference Category
H1 IEC 721-3-5 5K4/5B1/5C1/5S1/5F1/5M3
H2 IEC 721-3-5 5K3/5B1/5C1/5S1/5F1/5M2
H3 IEC 721-3-5 5K2/5B1/5C1/5S1/5F1/5M2
6.11 Safety
As this International Standard does not deal with any single defined application, and as the implementation
architecture is not part of the International Standard, it is not possible to include strict quantitative
requirements on safety. However, it is expected that manufacturers take into account safety aspects in
product design. Annex D details some aspects that should be considered as a minimum by manufacturers.
7 Test requirements
7.1 Objectives
It is the objective of this International Standard to provide specific reference criteria for test requirements and
reference tests for equipment claiming conformance with this family of International Standards for AVI/AEI
systems.
Wherever possible, the test requirements determined in this International Standard are formulated and
referenced to existing standards. This International Standard provides references to such standards by
classes.
All normative testing required in order to claim compliance with this International Standard shall be certified by
an AIB, approved by the nation state.
7.2 Operational parameters to be tested
7.2.1 General test requirements
7.2.1.1 Reliability
See 6.6.1.1.1.
14 © ISO 2005 – All rights reserved

7.2.1.1.1 Error Rates
The manufacturer shall satisfy the AIB (e.g. by means of calculation) that the system components have been
designed such that any relevant accuracy (maximum tolerated error rate) requirements determined in this
International Standard for a particular classification are met. (The form of such calculation is not
predetermined).
7.2.1.1.2 Failure Rates
The manufacturer shall satisfy the AIB (e.g. by means of calculation) that the system components have been
designed such that any relevant MTBF requirement determined or advised in this International Standard for a
particular classification is met. (The form of such calculation is not predetermined).
7.2.1.2 Availability
The form of availability check is not predetermined.
7.2.1.3 Lifetime
7.2.1.3.1 FE Lifetime
The manufacturer shall satisfy the AIB (e.g. by means of accelerated life cycle tests and/or calculation) that
the FE is expected to meet its claimed expected lifetime.
7.2.1.3.2 OBE Lifetime
The manufacturer shall satisfy the AIB (e.g. by means of accelerated life cycle tests and/or calculation) that
the OBE is expected to meet its claimed lifetime. (see 6.6.1.1.4).
7.2.1.4 Maintainability
See 6.6.1.1.2.
The OBE (excluding replaceable battery or external power source) shall not require maintenance throughout
its claimed lifetime.
NOTE Maintainability requirements for Fixed Equipment is considered to be a commercial agreement between the
buyer and seller, and is not covered by this International Standard.
7.2.1.5 Number of transactions/identifications per year (OBE):
The AIB shall ascertain to its satisfaction that the OBE has, at minimum, achieved the number of
transactions/identifications per year in accordance with the classification (as specified in this International
Standard) claimed by the manufacturer.
Where the OBE has a non-replaceable battery, such certification shall be based upon usage of an
internal/non-replaceable battery for the expected minimum
...