SIST EN ISO 17264:2010

SLOVENSKI STANDARD
SIST EN ISO 17264:2010
01-januar-2010
,QWHOLJHQWQLWUDQVSRUWQLVLVWHPL$YWRPDWLþQDLGHQWLILNDFLMDYR]LOLQRSUHPH
9PHVQLNL,62
Intelligent transport systems - Automatic vehicle and equipment identification - Interfaces
(ISO 17264:2009)
Systèmes intelligents de transport - Identification automatique des véhicules et de leur
équipement - Interfaces (ISO 17264:2009)
Ta slovenski standard je istoveten z: EN ISO 17264:2009
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
SIST EN ISO 17264:2010 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST EN ISO 17264:2010

---------------------- Page: 2 ----------------------

SIST EN ISO 17264:2010


EUROPEAN STANDARD
EN ISO 17264

NORME EUROPÉENNE

EUROPÄISCHE NORM
November 2009
ICS 03.220.20; 35.240.60
English Version
Intelligent transport systems - Automatic vehicle and equipment
identification - Interfaces (ISO 17264:2009)
Systèmes intelligents de transport - Identification
automatique des véhicules et de leurs équipements -
Interfaces (ISO 17264:2009)
This European Standard was approved by CEN on 28 October 2009.

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 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 Management Centre has the same status as the
official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, 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: Avenue Marnix 17, B-1000 Brussels
© 2009 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 17264:2009: E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------

SIST EN ISO 17264:2010
EN ISO 17264:2009 (E)
Foreword
This document (EN ISO 17264:2009) 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 "Intelligent transport systems".
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 May 2010, and conflicting national standards shall be withdrawn at the
latest by May 2010.
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.
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, 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 the United Kingdom.
2

---------------------- Page: 4 ----------------------

SIST EN ISO 17264:2010

INTERNATIONAL ISO
STANDARD 17264
First edition
2009-11-15


Intelligent transport systems —
Automatic vehicle and equipment
identification — Interfaces
Systèmes intelligents de transport — Identification automatique des
véhicules et de leurs équipements — Interfaces




Reference number
ISO 17264:2009(E)
©
ISO 2009

---------------------- Page: 5 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


COPYRIGHT PROTECTED DOCUMENT


©  ISO 2009
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 copyright@iso.org
Web www.iso.org
Published in Switzerland

ii © ISO 2009 – All rights reserved

---------------------- Page: 6 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
Contents Page
Foreword .iv
Introduction.v
1 Scope.1
2 Conformance .1
3 Normative references.2
4 Terms and definitions .2
5 Symbols and abbreviated terms .4
6 Requirements — AVI/AEI transaction profiles .4
6.1 General .4
6.2 AVI/AEI read and write transaction profile .5
6.3 Air interface definitions .5
7 Test methods .5
Annex A (normative) AVI/AEI Application interface using EN 12834/ISO 15628.6
Annex B (normative)  AVI/AEI transactions using ISO/IEC 18000 .14
Annex C (informative) AVI/AEI transaction examples.15
Bibliography.20

© ISO 2009 – All rights reserved iii

---------------------- Page: 7 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 17264 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).
iv © ISO 2009 – All rights reserved

---------------------- Page: 8 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
Introduction
This International Standard provides requirements for interoperable ITS transactions in an “Automatic Vehicle
Identification” (AVI), “Automatic Equipment Identification” (AEI) or “Electronic Registration Identification” (ERI)
context. An AVI/AEI transaction is based on defined sets of AVI/AEI functions and data attributes as specified
in this International Standard.
NOTE The principal definitions of AVI, AEI, ERI are to be found in ISO 14814, ISO 14815, ISO 14816, ISO 17261,
ISO/TS 17262, ISO 17263, ISO/TS 24534 (all parts) and ISO 24535.
This International Standard specifies an application interface for AVI/AEI systems, based on standardized air
interface protocols enabling interoperability between different AVI/AEI service providers.
In order to achieve full interoperability, AVI/AEI service providers will additionally have to agree on issues such
as:
⎯ protocol implementation conformance statements from manufacturers, detailing which optional features in
the AVI/AEI transaction and air interface protocol are actually being implemented and used;
⎯ any contractual agreements needed between AVI/AEI service providers in order to regulate the handling
of different AVI/AEI transactions.
NOTE The definitions and examples provided in this International Standard may also be used in an ERI context, and
those interested in this context are advised to also refer to ISO 24534 (all parts) and ISO 24535.
This International Standard has the following structure:
⎯ Clauses 1 to 5 comprise the Scope, Conformance, Normative references, Terms and definitions, and
Abbreviated terms.
⎯ In Clause 6, the AVI/AEI transaction requirements are defined, which are independent of any air interface
protocol.
⎯ In Annex A, the AVI/AEI application interface architecture is described in terms of its relation to the DSRC
communication architecture, based on EN 12834/ISO 15628.
⎯ In Annex B, the AVI/AEI application interface architecture is described in terms of its relation to the air
interfaces defined by the ISO/IEC 18000 series.
⎯ In Annex C, AVI/AEI transaction examples are provided.
© ISO 2009 – All rights reserved v

---------------------- Page: 9 ----------------------

SIST EN ISO 17264:2010

---------------------- Page: 10 ----------------------

SIST EN ISO 17264:2010
INTERNATIONAL STANDARD ISO 17264:2009(E)

Intelligent transport systems — Automatic vehicle and
equipment identification — Interfaces
1 Scope
This International Standard provides the specifications of:
⎯ common AVI/AEI transaction requirements, which define the common steps of any AVI/AEI transaction;
⎯ AVI/AEI application interface to standardized wireless protocols (referred to as the “Air Interface”)
supporting the AVI transaction requirements, so as to enable interoperability.
In Figure 1 the conceptual architecture model is shown for AVI transactions between “On-board Equipment”
and “Fixed Equipment”. The air interface concerns the reference point DELTA in ISO 14814.

Figure 1 — Overall conceptual reference architecture model showing the context
of AVI/AEI (ISO 14814)
This is an interface standard, adhering to the open systems interconnection (OSI) philosophy
(ISO/IEC 7498-1), and it is as such not concerned with the implementation choices to be realized at either
side of the air interface between the “Fixed Equipment” and “OBE”.
2 Conformance
Conformance may be claimed where equipment conforms to the provisions of this International Standard.
No specific performance tests are defined within this International Standard.
© ISO 2009 – All rights reserved 1

---------------------- Page: 11 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
3 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/IEC 8824-1, Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic
notation — Part 1
ISO 14816, Road transport and traffic telematics — Automatic vehicle and equipment identification —
Numbering and data structure
ISO 15628, Road transport and traffic telematics — Dedicated short range communication (DSRC) — DSRC
application layer
ISO/TS 17262, Automatic vehicle and equipment identification — Intermodal goods transport — Numbering
and data structures
ISO/IEC 18000-3, Information technology — Radio frequency identification for item management — Part 3:
Parameters for air interface communication at 13,56 MHz
ISO/IEC 18000-4, Information technology — Radio frequency identification for item management — Part 4:
Parameters for air interface communication at 2,45 GHz
ISO/IEC 18000-6, Information technology — Radio frequency identification for item management — Part 6:
Parameters for air interface communications at 860 MHz to 960 MHz
ISO/IEC 18000-7, Information technology — Radio frequency identification for item management — Part 7:
Parameters for active air interface communications at 433 MHz
CEN ISO/TS 24534-3, Automatic vehicle and equipment identification — Electronic Registration Identification
(ERI) for vehicles — Part 3: Vehicle data
EN 12834, Road Transport and Traffic Telematics — Dedicated Short Range Communication (DSRC) —
DSRC application layer
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1
action
function that an application process resident at the roadside equipment can invoke in order to make the on-
board equipment execute a specific operation during the AVI/AEI transaction
4.2
air interface
conductor-free medium between an OBE and the reader/interrogator through which the linking of the OBE to
the reader/interrogator is achieved by means of electro-magnetic signals
[ISO 14814:2006, definition 3.2]
4.3
attribute
application information formed by one or by a sequence of data elements, and managed by different actions
used for implementation of an AVI/AEI transaction
2 © ISO 2009 – All rights reserved

---------------------- Page: 12 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
4.4
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
[ISO 14815:2005, definition 4.19]
4.5
component
logical and physical entity composing on-board equipment supporting a specific functionality
4.6
element
in the context of DSRC, a directory containing application information in the form of attributes
4.7
fixed equipment
roadside equipment
equipment located at a fixed position along the road transport network, for the purpose of communication and
data exchanges with the on-board equipment of passing vehicles
NOTE See also reader.
4.8
on-board equipment
OBE
device on board or attached to the vehicle/equipment to perform the functionality of AVI/AEI
[ISO 14814:2006, definition 3.18]
4.9
on-board unit
minimum component of on-board equipment, whose functionality always includes at least the support of the
air interface
4.10
reader
device that transmits a signal as a means of initiating a response in a compatible OBE and subsequently
receives the modulated electro-magnetic response and decodes the data
[ISO 14814:2006, definition 3.22]
NOTE The reader is or can be, part of the roadside equipment/fixed equipment.
4.11
service
AVI/AEI
road transport related facility provided by a service provider
NOTE Normally this is a type of infrastructure, the use of which is offered to the user and for which the user may be
requested to identify his/her OBE.
4.12
service primitive (communication)
elementary communication service provided by the air interface to the application AVI/AEI
NOTE The invocation of a service primitive by an application process implicitly calls upon and uses services offered
by the lower protocol layers.
© ISO 2009 – All rights reserved 3

---------------------- Page: 13 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
4.13
service provider (AVI/AEI)
entity that reads the user's OBE and in return provides a service (AVI/AEI) to the user
5 Abbreviated terms
For the purposes of this document, the following abbreviations apply.
⎯ AEI automatic equipment identification
⎯ APDU application protocol data unit
⎯ ASN.1 abstract syntax notation one
⎯ AVI automatic vehicle identification
⎯ BST beacon service table (DSRC application layer)
⎯ DSRC dedicated short-range communications
⎯ EID element id (DSRC application layer)
⎯ I-KE initialization kernel element (DSRC application layer)
⎯ IID invoker id (DSRC application layer)
⎯ LID link id (DSRC application layer)
⎯ OBE on-board equipment
⎯ OBU on-board unit
⎯ PICS protocol implementation conformance statement
⎯ RSE road-side equipment
⎯ RTTT road transport and traffic telematics
⎯ VST vehicle service table (DSRC application layer)
6 Requirements — AVI/AEI transaction profiles
6.1 General
AVI/AEI transaction implies collecting data residing within an OBE that is compliant with ISO 14816,
ISO/TS 17262 and/or ISO/TS 24534-3 or writing such data to the OBE.
This International Standard defines two AVI/AEI transaction profiles, “AVI/AEI Read” and “AVI/AEI Read and
Write” that shall be implemented in the OBE and RSE supporting the AVI/AEI application.
6.1.1 AVI/AEI read transaction profile
An AVI/AEI read transaction profile shall comprise the set of service primitives as defined in Table 1.
4 © ISO 2009 – All rights reserved

---------------------- Page: 14 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
Table 1 — AVI/AEI read transaction profile
Required feature
Service primitive Parameter during Description
transaction
Initialization AVI/AEI attribute(s) Optional Depending on the air interface used, the RSE may
initialize the OBE before data exchange. This feature
is mandatory when air interface is compliant with
EN 12834/ISO 15628.
GET AVI/AEI attribute(s) Optional Action of reading data from the OBE.
Release None Optional After the completion of data exchange the RSE may
release the OBE.
6.2 AVI/AEI read and write transaction profile
An AVI/AEI read transaction profile shall comprise the set of actions as defined in Table 2.
Table 2 — AVI/AEI read and write transaction profile
Required feature
Service Primitive Parameter during Description
transaction
Initialization None Optional Depending on the air interface used, the RSE may
initialize the OBE before data exchange. This feature
is mandatory when air interface is compliant with
ISO 15628.
GET AVI/AEI attribute(s) Optional Action of reading data from the OBE.
SET AVI/AEI attribute(s) Mandatory Action of writing data to the OBE.
Release None Optional After the completion of data exchange the RSE may
release the OBE.
6.3 Air interface definitions
The detailed definitions of the AVI/AEI transaction are dependent on the air interface. Air interface definitions
are included in Annexes A and B.
7 Test methods
Test methods are not specified in this International Standard.
© ISO 2009 – All rights reserved 5

---------------------- Page: 15 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
Annex A
(normative)

AVI/AEI Application interface using EN 12834/ISO 15628
A.1 Usage of the DSRC application layer
AVI/AEI application uses the following services offered by DSRC application layer (as defined in
EN 12834/ISO 15628):
⎯ Initialization service, see Clause A.2.
⎯ Transaction phase, using GET, SET or ACTION service primitives, see Clause A.3.
⎯ Attribute definitions, see Clause A.4.
⎯ ASN.1 Container module named “AVIAEIInterfaceModule”, see Clause A.5.
In the remainder of this annex, the AVI/AEI-specific usage of the DSRC application layer is further specified.
A.2 Initialization phase
A.2.1 Overview
This clause provides an overview of the functionality of, and the information exchanges in, the initialization
phase.
The initialization service, by means of BST and VST exchanges, is defined in EN 12834/ISO 15628.
Sub-clauses A.2.2 and A.2.3 account for the AVI/AEI application-specific information that shall be included in
the BST and VST, respectively.
A.2.2 AVI/AEI application-specific contents of the BST
An RSE supporting AVI/AEI shall have configured its I-KE to carry the following information related specifically
to the AVI/AEI application(s):
⎯ the application identifier (AID) shall be equal to 11 (i.e. the value assigned for AVI);
⎯ the AVI/AEI application shall be qualified as a mandatory application;
⎯ the EID component may be omitted and, if present, shall be ignored by the ERI application;
⎯ the parameter component may be omitted or may be contained in the necessary data.
A.2.3 AVI/AEI application-specific contents of the VST
Each AVI/AEI application and corresponding contract shall be associated with an “AVI-ContextMark”, as
defined below. An OBE may support several AVI/AEI applications. If several AVI/AEI applications are
supported by an OBE, then the order in which the “AVI-ContextMarks” are presented in the VST shall
6 © ISO 2009 – All rights reserved

---------------------- Page: 16 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
correspond to the user's order of preference. The RSE shall normally use the first “AVI-ContextMark” that it
supports as presented in the VST.
An OBE supporting AVI shall have configured its I-KE to carry the following information related specifically to
the concerned AVI application:
⎯ the AID shall be equal to “AVI/AEI” (=11);
⎯ the EID value may be unique within the OBE throughout the complete DSRC session, and may be
logically associated with the corresponding e.g. “AVI-ContextMark” contained in the “Parameter”;
⎯ the “Parameter” may be of Container CHOICE type OCTET STRING and may comprise the e.g. “AVI-
ContextMark” as defined below, and may also be configured to carry additional AVI attributes.
The “AVI-ContextMark” has the following ASN.1 type definition:
AVI-ContextMark ::=SEQUENCE{
aVIProfile INTEGER {
  AttributeInTransactionPhaseOnly (0),
  Iso14816CS1AttrPointer (1), --CS1 appended in VST
  Iso14816CS2AttrPointer (2), --CS2 appended in VST
  Iso14816CS3AttrPointer (3),
  Iso14816CS4AttrPointer (4),
  Iso14816CS5AttrPointer (5),
  Iso14816CS6AttrPointer (6),
  Iso14816CS7AttrPointer (7),
  Iso14816CS8AttrPointer (8),
  ReservedforFutureISOUse1 (9),
  ReservedforFutureISOUse2 (10),
  ReservedforFutureISOUse3 (11),
  ReservedforFutureISOUse4 (12),
  ReservedforFutureISOUse5 (13),
  ReservedforFutureISOUse6 (14),
  ReservedforFutureISOUse7 (15),
  ReservedforFutureISOUse8 (16),
  ReservedforFutureISOUse9 (17),
  Private1To65535 (18),… }(0.65535),--Private profiles
profileVersion INTEGER(0.127,.) – Version control can be added
}
The value of the ISO 14816 “CSPointer” determines the ISO 14816 ASN.1 type included in the VST
“Parameter” as part of the “AVI-ContextMark”.
NOTE 1 If the AVIProfile value is set to the values 1 to 9, ISO 14816 attribute is included in the VST, if
AVIProfile value is set to 0, the attributes are sent in data exchange phase.
© ISO 2009 – All rights reserved 7

---------------------- Page: 17 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
NOTE 2 The above is the AVI/AEI application-specific contents of the VST. The complete VST is defined in
EN 12834/ISO 15628 and is given below for readability:
VST ::=  SEQUENCE {
fill  BIT STRING (SIZE(4))
profile Profile,
applications  ApplicationList,
obeConfiguration ObeConfiguration
}

where:
ApplicationList ::= SEQUENCE (0.127,.) OF
SEQUENCE{
aid  DSRCApplicationEntityID, --aid =11
eid  Dsrc-EID OPTIONAL,  --eid = e.g. 1
parameter Container OPTIONAL --e.g. 'AVI-ContextMark'
--depending on the value of the AVIProfile, see Note 1, an ISO 14816
attribute may also be included.
}
Container shall be of type 2 (OCTET STRING).
NOTE 3 An AVI/AEI application provider retains the ultimate control of his security domain, i.e. the security level and
the associated security mechanisms to be used within his system.
A.3 Transaction phase
After completion of the initialization phase, the appropriate RSE application is informed (by means of the notify
application beacon service) of the “AVI-ContextMark”(s) and associated EID(s). The RSE shall use the
functions defined in Clause 6 to complete the AVI/AEI transaction.
The RSE may invoke any sequence of AVI/AEI functions to complete the AVI/AEI transaction, provided that
they are supported by the “AVI-ContextMark”. The OBE shall respond to the AVI/AEI functions invoked by
the RSE, and shall not initiate any AVI/AEI functions (by usage of a request service primitive) on its side.
Due to the construction of the AVI/AEI part of the VST, each EID identifies a certain “AVI-ContextMark”
and shall be used by the RSE as a parameter of every function to unambiguously address data elements
within the context given by the “AVI-ContextMark”. More than one EID may be used in one session.
Both the type of attribute, and the maximum number of instances of an attribute is the implementation option
of the OBE and is outside the scope of this International Standard.
These implementation dependent aspects are referenced unambiguously by the ProfileVersion data
element in the “AVI-ContextMark”. In this way, the DSRC enables various AVI/AEI transaction types, such
as:
⎯ Type 1: AVI/AEI read Profile Using INITIALISATION
⎯ Type 2: AVI/AEI read Profile using INITIALISATION and GET
⎯ Type 3: AVI/AEI read/write Profile using INITIALISATION, GET and SET
⎯ Type 4: AVI/AEI read/write Profile using INITIALISATION, GET, SET or ACTION
⎯ Type 5: AVI/AEI read/write Profile using INITIALISATION, GET, SET and ACTION
8 © ISO 2009 – All rights reserved

---------------------- Page: 18 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
The supplier shall declare which transaction profile, type and set of attributes is supported in his OBE and
RSE in a “Protocol Implementation Conformance Statement” (PICS). The contents and format of the PICS
are outside the scope of this International Standard.
NOTE 1 Although not mandatory, it is recommendable that an RSE compliant with ISO 15628 support all service
primitives INITIALISATION, GET, SET and ACTION.
NOTE 2 The PICS can be a protocol specification or similar, which provides unambiguous implementation specification
of the AVI/AEI transaction type as well as air interface protocol details.
NOTE 3 ACTION service primitive shall be used for secure channelling of data between the OBE and RSE. Although
not mandatory, action types defined in ISO 14906 can be applied for such mechanisms.
© ISO 2009 – All rights reserved 9

---------------------- Page: 19 ----------------------

SIST EN ISO 17264:2010
ISO 17264:2009(E)
A.4 AVI/AEI attributes
Within the context of AVI/AEI, the AVI/AEI attributes listed in Table A.1 or a subset thereof shall be available
to perform an AVI/AEI transaction:
Table A.1 — AVI/AEI attributes
AttributeID Attribute Standard reference
AVI-ContextMark
0
CS1
1 ISO 14816
CS2
...