ETSI TR 102 644-2 V1.1.1 (2009-03)

Electromagnetic compatibility and Radio spectrum Matters (ERM); RFID Plugtests to investigate the interoperability of tags manufactured by different vendors; Part 2: Test plan and preliminary tests

DTR/ERM-TG34-006-2

General Information

• Status: Published
• Publication Date: 16-Mar-2009
• Technical Committee: ERM TG34 - ERM RF Identification Devices
• Current Stage: 12 - Completion
• Due Date: 12-Feb-2008
• Completion Date: 17-Mar-2009

Standards Content (Sample)

Technical Report
Electromagnetic compatibility
and Radio spectrum Matters (ERM);
RFID Plugtests to investigate the interoperability of tags
manufactured by different vendors;
Part 2: Test plan and preliminary tests

2 ETSI TR 102 644-2 V1.1.1 (2009-03)

Reference
DTR/ERM-TG34-006-2
Keywords
SRD, radio, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2009.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TR 102 644-2 V1.1.1 (2009-03)
Contents
Intellectual Property Rights . 5
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Abbreviations . 7
4 Influences On Tag Interoperability . 7
4.1 Preface . 7
4.2 Application Scenario . 7
4.3 Protocol Parameters . 8
4.4 Individual Tag Characteristics . 9
5 Definition of Tag Interoperability Tests . 10
6 Tag interoperability tests executed in application scenarios (RFID Plugtests) . 11
6.1 Introduction . 11
6.2 Purpose . 11
6.3 Arrangements . 11
6.4 Test Site . 12
6.5 Supervisors . 12
6.6 Confidentiality . 12
6.7 Sponsors . 12
6.8 Conduct of Tests . 13
6.9 Preparations . 13
6.10 Applications and Tests . 13
6.10.1 Application Set-up 1: Portal - Moving Pallet . 13
6.10.1.1 Application Overview and Purpose . 13
6.10.1.2 Application Set-up . 13
6.10.1.3 Test Preparation . 14
6.10.1.4 Test Procedure . 15
6.10.2 Application Set-up 2: Conveyor - Moving Case . 16
6.10.2.1 Application Overview and Purpose . 16
6.10.2.2 Application Set-up . 16
6.10.2.3 Test Preparation . 17
6.10.2.4 Test Procedure . 18
6.10.3 Application Set-up 3: Rack of DVDs - Shelf Reader . 18
6.10.3.1 Application Overview and Purpose . 18
6.10.3.2 Application Set-up . 18
6.10.3.3 Test Preparation . 19
6.10.3.4 Test Procedure . 20
6.10.4 Application Set-up 4: Retail Store - Handheld Reader . 21
6.10.4.1 Application Overview and Purpose . 21
6.10.4.2 Application Set-up . 21
6.10.4.3 Test Preparation . 22
6.10.4.4 Test Procedure . 23
6.11 Result Logging and Evaluation . 24
6.11.1 Final Report . 24
6.11.2 Real Time Result Evaluation (Local Result Monitoring Screens) . 24
6.11.3 Result Database . 24
6.11.4 noFillis CrossTalk Platform . 25
6.11.5 Reader Log Files . 26
ETSI
4 ETSI TR 102 644-2 V1.1.1 (2009-03)
7 Reader independent Tag Interoperability Tests (Preliminary TESTS) . 26
7.1 Introduction . 26
7.2 ASIC Specific Tests . 26
7.2.1 General . 26
7.2.2 Goal . 26
7.2.3 Tag ASICs under Test. 26
7.2.4 Test Setup . 27
7.2.5 Metrics . 30
7.2.6 Test Method . 30
7.2.7 Control Reader Configurations (Test Cases) . 31
7.3 Tag Specific Tests . 32
7.3.1 General . 32
7.3.2 Goal . 32
7.3.3 Tags under Test . 32
7.3.4 Test Setup . 33
7.3.5 Test Method . 34
Annex A: Bibliography . 36
History . 37

ETSI
5 ETSI TR 102 644-2 V1.1.1 (2009-03)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Report (TR) has been produced by ETSI Technical Committee Electromagnetic compatibility and Radio
spectrum Matters (ERM).
The present document is part 2 of a multipart deliverable covering RFID Plugtest that was performed at the MGI centre
in Neuss and at the VanDerLande premises in Veghel during the period 11th - 15th June 2008.
Part 1: "RFID Plugtests report";
Part 2: "Test plan and preliminary tests".
Introduction
Different applications, like conveyor belts or dock door portals, are characterized by different properties such as field
characteristics, tag population, speed and tag/reader density. These properties impose different requirements such as
read or write sensitivity and resistance to mutual coupling. When exposing tags of various types from different vendors
to application specific conditions, some tags might influence the operability of others, thereby being mutually
incompatible.
The goal of tag interoperability tests is to investigate issues of potential incompatibility that arise due to the use of tags
of various types from different vendors in application specific conditions.
The result is the test report made publicly available via the ETSI web-page. Prior to the RFID Plugtests, preliminary
tests were conducted using a well documented, dedicated test reader with one antenna port and special measurement
equipment for extended evaluation options (referred to as the control reader). In order to gain the best understanding of
possible anomalies these preliminary tests were conducted using two different set-ups. The ASIC specific test set-up
focused on the inventory of multiple tags hard wired to the control reader, (i.e. eliminating the influences of the RF
field). The tag specific test set-up focused on the inventory of multiple tags under application specific conditions (using
an antenna to generate a RF field instead of hard wiring the tags to the control reader).
In the second step the ETSI RFID Plugtests were executed in application scenarios using commercially available
equipment. As the results of the preliminary tests merely provide a basis for understanding potential issues, only the
results of the ETSI RFID Plugtests are included in Part 1 of TR 102 644 [i.6].
ETSI
6 ETSI TR 102 644-2 V1.1.1 (2009-03)
1 Scope
The present document defines a test plan for tag interoperability tests. The main objective of such tests is to confirm that
mixed populations of tags (tags of different types and/or from different vendors) can be identified correctly. The tests
are defined in a two-step approach.
The present document identifies the main factors influencing tag interoperability including application scenarios,
protocol parameters and individual tag characteristics. Each of these aspects is addressed in detail with the aim of
providing a test plan and evaluation matrices for tag interoperability tests. Protocol specific issues in the present
document are focused on the EPCglobal Class 1 Generation 2 (C1G2) air interface specification [i.2] and the air
interface specification ISO/IEC 18000-6 Type C [i.3].
The present document served as basis for carrying out ETSI Plugtests (RFID Interoperability Event) in June 2008.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
Not applicable.
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
[i.1] ETSI TS 102 237-1: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON) Release 4; Interoperability test methods and approaches; Part 1: Generic approach to
interoperability testing".
TM
[i.2] EPCglobal: "EPC Radio-Frequency Identity Protocols; Class-1 Generation-2 UHF RFID;
Protocol for Communications at 860 MHz - 960 MHz", Version 1.1.0.
NOTE: Available at http://www.epcglobalinc.org/standards/uhfc1g2/uhfc1g2_1_1_0-standard-20071017.pdf.
ETSI
7 ETSI TR 102 644-2 V1.1.1 (2009-03)
[i.3] 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".
[i.4] Void.
[i.5] ETSI EN 302 208-1 (V1.2.1): "Electromagnetic compatibility and Radio spectrum Matters (ERM);
Radio Frequency Identification Equipment operating in the band 865 MHz to 868 MHz with
power levels up to 2 W; Part 1: Technical requirements and methods of measurement".
[i.6] ETSI TR 102 644-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); RFID
Plugtests to investigate the interoperability of tags manufactured by different vendors;
Part 1: RFID Plugtests report".
[i.7] CEPT/ERC REC 70-03: Relating to the use of Short Range Devices (SRD).
3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASIC Application Specific Integrated Circuit
EUT Equipment Under Test
RFID Radio Frequency IDentification
QE Qualified Equipment
4 Influences On Tag Interoperability
4.1 Preface
The main factors influencing tag interoperability are the application scenario, protocol parameters, and individual tag
characteristics. Each of these factors is addressed in detail in the following clauses. However due to the large number of
variables associated with application scenarios and protocol parameters, it is only possible to cover the main factors
influencing tag behaviour. Since there could be issues in assigning interrogator related characteristics either to the
application scenario or to the protocol parameters, the following convention is adopted: software definable
characteristics are assigned to the protocol parameters while all others are assigned to the application scenario.
4.2 Application Scenario
The application scenario describes the set-up in which an RFID interrogator and tags are used. The main characteristics
of an application scenario include:
• Environment:
- All aspects that have a certain influence on an application but are not part of the application itself (like
surrounding material, noise sources of any kind e.g. mobile phones).
• Reader antenna arrangement:
- Position and orientation of the reader antennas in a set-up.
- Number of reader antennas.
- Type of reader antennas.
• Tag arrangement:
- Position and orientation of the tags in a set-up.
- Number of tags.
ETSI
8 ETSI TR 102 644-2 V1.1.1 (2009-03)
- Type of tags (different vendors/models).
• Relative movement between reader antennas and tags:
- Speed.
- Path:
E.g. pallet moving through portal (tags moving).
E.g. handheld reader (reader antenna moving).
• Pallet / Case / Item characteristics:
- Materials.
- Arrangement.
4.3 Protocol Parameters
The protocol parameters describe the protocol settings, as well as other software options associated with a particular
application set-up. The main protocol parameters are (C1G2 specific where applicable):
• Link rates:
- Forward link.
- Return link.
• Modulation/Encoding:
- Modulation type (forward link).
- Modulation depth (forward link).
- Duty cycle (forward link).
- Encoding (return link).
• CW:
- Power.
- Frequency.
• Link timing:
- In most cases not selectable!
• Protocol flow:
- Command sequence.
- Collision-arbitration concept (Q protocol).
- Function:
Selection/inventory only.
Access - write.
• Session usage:
- Session flag.
- Selected flag.
ETSI
9 ETSI TR 102 644-2 V1.1.1 (2009-03)
- A B, B A inventory.
• TRext usage:
- Pilot tone.
- No pilot tone.
• Reader antenna switching:
- Sequence.
- Timing.
- Interrelation with protocol concepts (e.g. inventory round).
4.4 Individual Tag Characteristics
The individual tag characteristics describe attributes that, due to variations between different tags, may influence tag
interoperability. Some of these attributes are defined for the RFID Plugtests and assume tags operating under
ISO/IEC 18000-6 [i.3].
• Read range:
- The sensitivity of a tag typically expressed as forward link range for a given transmit level.
• Orientation tolerance:
- The sensitivity of a tag in terms of its read range if it is rotated away from its preferred orientation.
• Frequency tolerance:
- The sensitivity of a tag in terms of its read range at various carrier frequencies from 860 MHz to
960 MHz.
- Tags with high frequency tolerance typically show less variation in sensitivity if attached to different
materials.
• Interference tolerance:
- Describes the degradation in read range of tags from interference generated by other nearby interrogators
(e.g. dense interrogator environment).
• Backscatter range:
- The strength of a backscatter response from a tag for a given downlink field level in terms of return link
range.
- The range of the return link for passive tags typically is greater than the range of the forward link.
- The efficiency of the hardware design for generating the backscatter signal.
• Backscatter timing:
- The interval between the instant that the interrogator ceases transmitting its modulated signal and the
instant that the tag starts to transmit its backscatter response.
• Write range:
- The write sensitivity of the tag, i.e. the maximum forward link range at which it is possible to write data
into a tag.
• Write time:
- The time taken to write x bits into a tag.
ETSI
10 ETSI TR 102 644-2 V1.1.1 (2009-03)
• Tag proximity:
- Describes the degradation in read range of a tag when positioned in proximity to another tag / other tags.
- Detuning immunity.
- Mutual coupling.
• Tag flags persistence time:
- Persistence time of the S1, S2, S3 and SL flags.
• Tag RNG probability:
- Probability of a tag's RNG to roll a 1 in a specific time slot.
5 Definition of Tag Interoperability Tests
Tag Interoperability Test: ETSI defines interoperability as the "ability of two systems to interoperate using the same
communication protocol" ([i.1], p.8). Furthermore, the purpose of interoperability testing is identified as to "prove that
end-to-end functionality between (at least) two communicating systems is as required by the standard(s) on which those
systems are based" ([i.1], p.9). ETSI clearly highlights that each interoperability test configuration includes one, and
only one, subject of test called the Equipment Under Test (EUT) ([i.1], p.13).
For the purposes of the RFID Plugtests tag interoperability is defined as the ability of an RFID interrogator (Qualified
Equipment - QE) to interoperate with a population of RFID tags (Equipment Under Test EUT) using the same
communication protocol, wheras.
Figure 1 shows the architecture for a tag interoperability test based on this approach (this is modified from figure 7 of
[i.1]) where the QE is an RFID interrogator. The EUT comprises a number of tags (two or more) typically of mixed
types and/or from different vendors. Thus individual tags can be treated as components of the EUT and interoperability
issues will be seen as the inability of the QE to communicate with one or more of these components.

Figure 1: Tag Interoperability Test Setup
This clause introduces the structure of tests for tag interoperability. The tests have in common that they are performed
for homogenous tag populations (all tags of the same type) and mixed tag populations (different types of tags are used).
The outcome of the tests is assessed mainly by comparing the results for the homogenous and mixed tag populations.
The tests are sub-divided into two steps:
1) Tag interoperability tests that are interrogator independent (preliminary tests) focus solely on issues that
influence tag-to-tag interoperability. In particular these tests are executed using a control reader (as described
in clause 6). The aim of these tests is to gain knowledge about potential tag-to-tag interoperability issues.
2) The ETSI RFID Plugtests are tag interoperability tests that are performed under various application scenarios.
The tests are performed with a range of commercially available interrogators and tags. Further details are
defined in clauses 6 and 7.
ETSI
11 ETSI TR 102 644-2 V1.1.1 (2009-03)
6 Tag interoperability tests executed in application
scenarios (RFID Plugtests)
6.1 Introduction
This clause defines tag interoperability tests that are performed in a series of real life scenarios, which are representative
of applications in the logistics and retail industries. The tests include the movement of tagged cartons on pallets moving
through dock doors and the movement of tagged objects on conveyors. In addition tests use both shelf readers and hand
held readers. For the tests commercially available interrogators and tags are used.
th
The tests were carried out at an ETSI Plugtests event (RFID Interoperability Event), which took place from 11 to
th
15 June 2008 at the Metro Group - RFID Innovation Center in Neuss (Germany) and at VanDerLande Industries in
Veghel (The Netherlands).
Details are discussed below.
6.2 Purpose
The purpose of the Plugtests described herein is to investigate if there is a satisfactory level of interoperability between
RFID equipment (interrogators and tags) supplied by different vendors. The main objective of the tag interoperability
tests is to confirm that mixed populations of tags (tags of different types and/or from different vendors) can be identified
correctly by interrogators provided by different manufacturers. This information is of major strategic importance to
those end-users who wish to use RFID on a global basis.
The results from the Plugtests is published in TR 102 644-1[i.6], which is documented in a way that avoids disclosure
of the performance of individual manufacturer's equipment (tags and interrogators).
6.3 Arrangements
The Plugtests took place from 11-15 June 2008. The deadline for registration was 22 May 2008. In order to ease
logistics it was recommended that participants ship equipment in advance with a shipment deadline of 27 May 2008.
To allow adequate time for preparation of the test set-ups, tags were provided well in advance with a shipment deadline
of 20 May 2008. Details about the preparations for individual tests are covered further below in this clause.
The following days were allocated for carrying out tests:
• Wednesday, 11 June 2008:
- Application Set-up 3: Rack of DVDs - Shelf Reader.
- Application Set-up 4: Retail Store - Handheld Reader.
• Thursday, 12 June 2008:
- Application Set-up 1: Portal - Moving Pallet.
• Friday, 13 June 2008:
- Application Set-up 2: Conveyor - Moving Case.
The other days were left open in order to allow for investigation of unresolved issues, repetition of individual tests,
review of results, and any other business.
Tests commenced at 9 a.m. at each of the test days.
Participating tag and ASIC manufacturers were each requested to provide at least 1 000 tags for the Plugtests. The tags
were programmed by Metro during test preparation.
ETSI
12 ETSI TR 102 644-2 V1.1.1 (2009-03)
Reader manufacturers were invited to provide interrogators optimized for each of the four applications mentioned above
(since the tests did not take place in parallel but on separate days, the same interrogators may have been reused for
different applications). The interrogators used in application setups 1 to 3 were fitted with four SMA female connectors
for connection to the feeder cables from the antennas at the application set-ups. For interrogators used in application
setup 4 (handheld readers) a specification of the built-in antenna (e.g. radiation pattern) were provided as a reference.
All interrogators conformed to the technical requirements of EN 302 208-1 [i.5]. Manufacturers supplied suitable
software and any specialist hardware necessary to drive the interrogators and to display the results.
In order to simplify logging of the results and real time analysis, it was desirable that interrogators provide an interface
to the data logging platform, which was used at the test site. For those interrogators that did not support the CrossTalk
platform, the results were fed manually into the evaluation system. In this case reader manufacturers were required to
provide example log files in advance (deadline 27 May 2008). For detailed information about the evaluation system and
processing of the results please see further below.
An interface validation point was made available at the test site in order to allow reader vendors to verify their interface
to the evaluation system prior to the commencement of the tests.
Mains power points with 230 V at 50 Hz were provided at the test site.
6.4 Test Site
The Plugtests mainly took place at the Metro Group - RFID Innovation Center in Neuss (Germany). The address is:
METRO Group - RFID Innovation Center
Mainstraße 113-119 (access via Kruppstrasse)
41469 Neuss - GERMANY
Tel: [phone]
Fax: [phone]
The tests for Application Setup 2 (Conveyor - Moving Case) were carried out at VanDerLande Industries in Veghel
(The Netherlands) on Friday, 13 June 2008. A coach carried the participants and equipment from Düsseldorf (Nikko
hotel) to Veghel (test site) on Friday morning and back on Friday evening. The address was:
Vanderlande Industries Nederland B.V. (Headquarters)
Vanderlandelaan 2
5466 RB Veghel
Phone: [phone]
Fax: [phone]
Details to follow (floor plans).
6.5 Supervisors
The Plugtests was managed by four neutral test supervisors. These were John Falck (Chairman ERM_TG34),
EPCglobal Inc. (to be confirmed), Josef Preishuber-Pfluegl and Manfred Jantscher (both CISC Semiconductor
Design+Consulting GmbH). All test supervisors signed the ETSI NDA and treated the results from each manufacturer's
equipment in the strictest confidence.
6.6 Confidentiality
As a precondition of participating in the RFID Plugtests, all participants were required to sign the ETSI NDA. Any
information of a confidential nature that participants may have acquired during the course of the RFID Plugtests relating
to other participants and their equipment was agreed to only be used only for the purpose of these Plugtests and not be
divulged to any person not present at the Plugtests without the written agreement of the owner of the confidential
information.
6.7 Sponsors
The Plugtests were sponsored by the Information Society of the European Commission.
ETSI
13 ETSI TR 102 644-2 V1.1.1 (2009-03)
6.8 Conduct of Tests
The individual application tests were conducted according to the guidelines provided in clause 6.11. The representatives
from each manufacturer assisted the test supervisors in the conduct of the tests. However only test supervisors were
permitted to record test results. The results of the tests were recorded according to the guidelines in clause 6.11. The
recorded results were not directly traceable to individual manufacturers.
6.9 Preparations
Metro provided means to conduct tests for application Set-ups 1, 3 and 4. VanDerLande Industries provided means to
conduct tests for application Set-up 2.
6.10 Applications and Tests
This clause discusses details about the individual test application set-ups. It covers the description of the set-ups
including the purposes of the tests, guidelines for preparations, and guidelines for conducting the tests.
6.10.1 Application Set-up 1: Portal - Moving Pallet
6.10.1.1 Application Overview and Purpose
Portal set-ups, like dock door portals, are very common in the supply chain. Typically, a number of tagged cases/items
placed on a tagged pallet are moved through a portal with the aim to inventory the pallet, case, and item tags.
The purpose of the tests described in this clause is to verify that there is a satisfactory level of interoperability between
tags and interrogators supplied by different vendors when used in a typical portal scenario.
In the tests, pallets of tagged cartons (homogenous and mixed tag populations) were moved through a portal by a
battery powered pallet truck. The tags were identified by the interrogator connected to the portal antennas.
6.10.1.2 Application Set-up
The test application set-up basically comprises a portal fitted with four antennas, an interrogator connected to these
antennas, a pallet of tagged cartons, and a battery powered pallet truck.
The portal including the antennas were made available by Metro. The interrogators were provided by the participating
reader vendors (one per vendor). The tags were provided by the participating tag vendors. The pallet set-up were
prepared in advance by Metro.
There were several pallets with different tag populations. With the exception that different tag types were attached to
the cartons, all pallets were identical. The cartons included material that influences the readability of RFID tags
(e.g. detergent). Details are discussed in further below.
Table 1 summarizes the application parameters for the portal application set-up. Table 2 summarizes the corresponding
protocol parameters.
ETSI
14 ETSI TR 102 644-2 V1.1.1 (2009-03)
Table 1: AS1 - Application Parameters
Parameter Description Remark
Environment Representative of a distribution centre There might be several portals used
Dock door portals for testing in parallel (avoid influences
from adjacent portals - sufficient
distance; minimize number of variables
in tests!)
Antenna arrangement Typical dock door portal Interrogators provided by different
4 antennas (2 left, 2 right) connected vendors were connected to the
to a single interrogator antennas
Circularly polarized antennas
Tag arrangement Tags attached to cartons Several pallets with different tag
Cartons arranged on pallet populations were prepared in advance
Placement of tags on cartons and
arrangement of cartons on pallet
optimized as in real application set-up
(Metro know-how)
Movement Battery powered pallet truck used at Light curtain was used to start
full speed to move pallet through portal interrogator operation
Straight movement path Interrogator inventoried for 2 s
Case characteristics All cartons were identical in order to
minimize number of variables
Cartons included material that
influences readability of tags
(e.g. detergent)
Table 2: AS1 - Protocol Parameters
Parameter Value Remark
Data rates, modulation, encoding Defined by reader vendor DRM (Miller sub carrier encoding) was
required
CW power, CW frequency, channel Defined by reader vendor ERC Rec 70-03 [i.7], annex 11
sharing technique Requirements of EN 302 208-1 [i.5]
were met
Protocol flow, session usage, TRext Defined by reader vendor Reader vendors were allowed to
usage, antenna switching, other (like Q optimize their interrogator for
parameter settings) application set-up

NOTE: Reader vendors were required to provide test supervisors with written details of the specific configuration
parameters used during the tests.
6.10.1.3 Test Preparation
Portals: Provided by Metro. It was anticipated that two or three portals would be available in order to run the tests in
parallel. There was sufficient separation between the portals used for the tests to minimize interference. The portals
were equipped with a light curtain or similar to indicate the approach of a pallet and provide an output by means of a set
of "dry" contacts for connection to an interrogator. Specification of portals including antennas were provided by Metro.
Pallets: Provided by Metro. The pallets for testing were prepared prior to the tests. With the exception that different
tags were attached to the cartons, all pallets were identical. The pallets carried a number of tagged cartons (at least 50).
All cartons were identical and included material that influences the readability of tags (e.g. detergent). The placement of
tags on cartons and arrangement of cartons on pallet was optimized (Metro know-how).
ETSI
15 ETSI TR 102 644-2 V1.1.1 (2009-03)
Pallets with homogenous tag populations (tags of same type and from same vendor) and pallets with mixed tag
populations (tags of different types and/or from different vendors) were prepared in the following way:
• There was a pallet with a homogenous tag population for each tag type provided for testing:
- The number of pallets with a homogenous tag population depended on the actual number of different tag
types available for the tests. As an example for three different tag types A, B, and C there were the
following homogenous tag population pallets:
Pallet with only type A.
Pallet with only type B.
Pallet with only type C.
• There were pallets with mixed tag populations. Tags of different types were distributed equally on the pallet:
- The number of pallets with mixed tag populations depended on the number of different tag types
available for the tests. As an example for three different tag types A, B, and C there might have been the
following pallets with mixed tag population (the number of tags of each type on a pallet should be the
same):
Pallet with all three types A, B, and C.
Pallet with types A and B only.
Pallet with types A and C only.
Pallet with types B and C only.
- There might also have been pallets with a known imbalance in the number of tags of different types:
e.g. pallet with 95 % tags of type A and only 5 % tags of type B.
• A complete set of pallets (homogenous and mixed tag population types) was provided for each portal used for
the tests.
A number of tagged cartons (at least 5 per tag type) was prepared separately in order to allow for unplanned additional
tests.
As soon as the actual number of participating tag vendors (number of different tag types) was known, a detailed plan of
the test pallets including the arrangement of cartons, placement of tags, types of tags, and EPCs of tags was provided by
Metro. A number was assigned to each pallet, which was made visible on the pallet and used for evaluation of the
results.
Information about the test pallets was fed into the database of the evaluation system prior to the tests. This included the
EPCs of the individual tags and their association with the test pallets (pallet number).
6.10.1.4 Test Procedure
The following steps describe the test procedure used.
1) The interrogator under test was connected to the four antennas mounted at the portal using the SMA
connectors/cables.
2) The interrogator under was connected test to the light curtain or similar used to indicate the approach of a
pallet.
3) The interface between the interrogator under test and the evaluation system was configured according to the
guidelines in clause 6.11.4. If no direct link to the evaluation system was available, the interrogator was
configured to generate log files according to the guidelines in clause 6.11.5 (the same format as the sample log
file that was provided prior to the tests).
4) The interrogator was configured under test for optimized operation in the portal application consistent with the
technical requirements of EN 302 208-1 [i.5].
ETSI
16 ETSI TR 102 644-2 V1.1.1 (2009-03)
5) The battery powered pallet truck was prepared with a pallet under test for moving through the portal.
6) For evaluation of the results, the application set-up (portal), the actual portal used for the test (portal number),
the interrogator under test (anonymized), the pallet used for the test (pallet number), and the test run number
were recorded. It was hoped to support this process by the use of a graphical user interface on a local monitor.
If log files were generated, the required data was recorded and linked manually during parsing of the log files
into the evaluation system.
7) The pallet was moved through the gate at full speed using the battery powered pallet truck:
a) The interrogator started its operation when triggered by the light curtain or similar.
b) The interrogator stopped inventory 2 s after starting.
c) Each tag inventory was recorded including timestamp, EPC, antenna number, and RSSI value.
8) Steps 6 and 7 were repeated three times (three test runs).
9) Steps 5 to 8 were repeated for each of the prepared pallets.
10) Steps 1 to 9 were repeated for each interrogator under test.
6.10.2 Application Set-up 2: Conveyor - Moving Case
6.10.2.1 Application Overview and Purpose
In typical conveyor belt applications (e.g. logistics, baggage handling) tagged cases, including mixed items, (materials)
move sequentially past interrogators with the aim to inventory the tagged objects.
The purpose of t
...