Professional Documents
Culture Documents
Reference number of document: ISO/IEC JTC1 SC31 WG4 SG3 18000-6 Proposal
Secretariat: ANSI
Warning
This document is not an ISO International Standard. It is distributed for review and comment. It is subject to
change without notice and may not be referred to as an International Standard.
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of
which they are aware and to provide supporting documentation.
Copyright notice
This ISO document is a working draft or committee draft and is copyright-protected by ISO. While the
reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards
development process is permitted without prior permission from ISO, neither this document nor any extract
from it may be reproduced, stored or transmitted in any form for any other purpose without prior written
permission from ISO.
Requests for permission to reproduce this document for the purpose of selling it should be addressed as
shown below or to ISO’s member body in the country of the requester:
[Indicate :
the full address
telephone number
fax number
telex number
and electronic mail address
as appropriate, of the Copyright Manager of the ISO member body responsible for the secretariat of the TC or
SC within the framework of which the draft has been prepared]
Reproduction for sales purposes may be subject to royalty payments or a licensing agreement.
ii
ISO/IEC 18000-6
Contents
Foreword ........................................................................................................................................................ v
Introduction ................................................................................................................................................... vi
1 Scope.................................................................................................................................................. 1
2 Conformance ...................................................................................................................................... 1
3 Normative references.......................................................................................................................... 1
4 Terms and definitions......................................................................................................................... 2
5 Symbols (and abbreviated terms) ....................................................................................................... 3
6 Summary Of Commands..................................................................................................................... 3
6.1. Command Set ..................................................................................................................................... 3
6.2 Proprietary Commands....................................................................................................................... 4
6.3 Read Modes........................................................................................................................................ 5
6.3.1 Single Bit Read....................................................................................................................................... 5
6.3.2 Multiple Bit Read.................................................................................................................................... 5
7 Architectural Notes............................................................................................................................. 5
7.1 ID_FLAG ............................................................................................................................................. 5
7.2 PRE_SEL_FLAG ................................................................................................................................. 6
7.3 VDDW_OK........................................................................................................................................... 6
7.4 Address Register................................................................................................................................ 6
7.5 Status Register ................................................................................................................................... 6
7.6 Parameters ......................................................................................................................................... 6
7.7 Transmitted CRC ................................................................................................................................ 6
7.8 Command Structure............................................................................................................................ 7
8 Block Diagrams .................................................................................................................................. 8
9 Command Descriptions ...................................................................................................................... 9
9.1 Wake_up............................................................................................................................................. 9
9.1.1 Standard Wake_up, Reference 1....................................................................................................... 10
9.1.2 Wake_up, Read ID_FLAG, sleep if set, Reference 2.......................................................................... 10
9.2 Multiple Tag Read............................................................................................................................. 10
9.2.1 Command Phases............................................................................................................................. 10
9.2.2 Instant Elimination Mode for Class Sortation ................................................................................... 10
9.2.3 Start Multi–Tag-Read, Reference 3.................................................................................................... 11
9.2.4 Start Multi–Tag-Read at Address 0, Reference 4............................................................................... 11
9.2.5 Start Multi–Tag-Read at Address 2, Reference 5............................................................................... 11
9.2.6 Orthogonal Read, Reference 100 ...................................................................................................... 11
9.3 Sleep_if............................................................................................................................................. 11
9.3.1 Sleep_ if ID_FLAG is set, Reference 8............................................................................................... 11
9.3.2 Sleep_ if ID_FLAG is clear, Reference 9............................................................................................ 11
9.3.3 Sleep_ if PRE_SEL_FLAG is set, Reference 10................................................................................. 12
9.3.4 Sleep_ if PRE_SEL_FLAG is clear, Reference 11.............................................................................. 12
9.4 Set/Clear Flags.................................................................................................................................. 12
9.4.1 Set ID_FLAG, Reference 12............................................................................................................... 12
9.4.2 Clear ID_FLAG, Reference 13 ........................................................................................................... 12
9.4.3 Set PRE_SEL_FLAG, Reference 14................................................................................................... 12
9.4.4 Clear PRE_SEL_FLAG, Reference 15................................................................................................ 12
9.5 Read Tag Flags (Single Bit Reads) .................................................................................................... 12
9.5.1 Read ID_FLAG, Reference 16............................................................................................................ 12
9.5.2 Read PRE_SEL_FLAG, Reference 17................................................................................................ 12
9.5.3 Read PRE_SEL_FLAG. Sleep if Clear, Reference 18......................................................................... 12
9.5.4 Read WRT_PROT Bit, Reference 19.................................................................................................. 12
The table of contents is an optional preliminary element, but is necessary if it makes the standard easier to
consult. The table of contents shall be entitled “Contents” and shall list clauses and, if appropriate, subclauses
with titles, annexes together with their status in parentheses, the bibliography, index(es), figures and tables. The
order shall be as follows: clauses and subclauses with titles; annexes (including clauses and subclauses with
titles if appropriate); the bibliography; index(es); figures; tables. All the elements listed shall be cited with their full
titles. Terms in the “Terms and definitions” clause shall not be listed in the table of contents.
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 3.
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 part of ISO 18000 may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
International Standard ISO 18000, Part 6 was prepared by Technical Committee ISO/TC 000, TC title,
Subcommittee SC 0, SC title.
This second/third/... edition cancels and replaces the first/second/... edition (ISO nnn-n:19xx), [clause(s) /
subclause(s) / table(s) / figure(s) / annex(es)] of which [has / have] been technically revised.
ISO 18000 consists of the following parts, under the general title Introductory element — Main element:
Part 1 – Generic Parameters for Air Interface Communication for Globally Accepted Frequencies
The foreword shall appear in each standard. It shall not contain requirements, figures or tables.
In addition to the appropriate boilerplate text (see above) give as many of the following as are appropriate:
— an indication of any other international organization that has contributed to the preparation of the standard;
— a statement that the standard cancels and replaces other documents in whole or in part;
— a statement of significant technical changes from the previous edition of the standard;
— a statement specifying which annexes are normative and which are informative.
Introduction
This specification is for the design of the ISO 18000-6 Air Interface. It includes the signal characteristics and
command set used in communicating between the reader and the tag.
This proposal is based on Region 1 (European) regulations and Region 2 (US FCC part 15) regulations but also
trying to account for the proposed changes to Region 1 regulations. Below is a summary of the system’s
characteristics.
The characteristics of the transmitted signal generated by the reader is listed below in Table 1-2
Table 1-2 Physical link specifications— forward link (reader to the tag)
F3 Interrogator Transmit Region 1: The current maximum for Region 1 is 27 dBm ERP
Power Region 2: The current maximum is 30 dBm output from the
reader, and 4W (36 dBm) EIRP from the reader transmit
antenna.
Region 3: Adopt Region 2 where possible, otherwise Region 1
or better.
F4 Interrogator Transmit As permitted by local regulation
Spurious Emissions, Region 1: ETS EN 300-220-1
Region 2: As permitted by FCC
Region 3: Adopt Region 2 where possible, otherwise Region 1
or better.
Out of band emission: less than 250nW EIRP
Below in Table 1-3 are listed the characteristics of the return signal from the tag
Table 1-3 Physical link specifications – backscatter return link (tag to the reader)
R 11 Preamble None
RawData
Tp Ts
Tci Tci Tci
Clocki
Tch
The forward link (reader to tag) communication is achieved by sending one or more RF pulses to the tag, which
are received by the tag circuitry as RawData pulses.
Frame Markers and Data are transmitted at an interval (frame length) within the constraints of the underlying
implementation technology and the regional radio regulations. In Region 2, the frame length may be typically 10
microseconds
To send a frame marker (clock only), the reader transmits 1 pulse. To send a “0”, it transmits 2 pulses, and to
send a “1” it transmits three. A “Q”, (Quad, or four pulses), is also defined (not shown) to indicate the start of a
Proprietary Command.
In addition to interpreting the RawData pulses as data “0s” and “1s”, the tag simultaneously uses the RawData to
develop its internal Clock, Clocki. In this way the tag operation is fully self-clocking and synchronized with the
reader operation.
RawData
Tp
Tci Tci Tci
Clocki
Tch
Tco Tco Tco
Clocko
Tch
Data_Tx
LdAntenna
Tag communication to the reader is by RF “backscatter”, where the tag’s antenna impedance is modulated by its
data, and the impedance changes are sensed by the reader’s receiver circuitry. Tag data are sent by the tag in
response to the appropriate commands and data from the reader, a single bit per frame. The tag’s responses are
fully synchronized, bit by bit, with the reader’s transmissions.
Antenna impedance modulation is achieved when a Data_Tx signal from the digital logic section indicates within
which frame the tag will send a response. This is logically ANDed with an output clock pulse, Clocko, to form the
Ld Antenna signal.
The introduction is an optional preliminary element used, if required, to give specific information or commentary
about the technical content of the standard, and about the reasons prompting its preparation. It shall not contain
requirements.
The introduction shall not be numbered unless there is a need to create numbered subdivisions. In this case, it
shall be numbered 0 with subclauses being numbered 0.1, 0.2, etc. Any numbered figure, table, displayed
formula or footnote shall be numbered normally beginning with 1.
1 Scope
A paragraph.
The Scope clause shall appear at the beginning of each standard and define without ambiguity the subject of
the standard and the aspect(s) covered, thereby indicating the limits of applicability of the standard or
particular parts of it. It shall not contain requirements.
The scope shall be succinct so that it can be used as a summary for bibliographic purposes.
It shall be worded as a series of statements of fact. Forms of expression such as “This International Standard
specifies [establishes] [gives guidelines for] [defines terms] … ” shall be used.
Statements of applicability of the standard shall be introduced by the wording “This International Standard is
applicable to … ”.
The clauses in each standard or part shall be numbered with arabic numerals, beginning with 1 for the “Scope”
clause. The numbering shall be continuous up to but excluding any annexes. Numbers given to the clauses of
an annex shall be preceded by the letter designating that annex followed by a full-stop. The numbering shall
start afresh with each annex.
Each clause shall have a title, placed immediately after its number, on a line separate from the text that follows
it.
2 Conformance
A paragraph.
The Conformance clause is only required in some standards in the Information technology field.
Requirements concerning the conformance clause are not covered by the ISO/IEC Directives, Part 3, 1997,
but by ISO/IEC TR 10000-1[1].
3 Normative references
The following normative documents contain provisions which, through reference in this text, constitute
provisions of this part of ISO 18000. For dated references, subsequent amendments to, or revisions of, any of
these publications do not apply. However, parties to agreements based on this part of ISO nnn are
encouraged to investigate the possibility of applying the most recent editions of the normative documents
indicated below. For undated references, the latest edition of the normative document referred to applies.
Members of ISO and IEC maintain registers of currently valid International Standards.
i
ISO/IEC 18000-6
The Normative reference(s) clause is an optional element that gives a list of the normative documents to
which reference is made in the standard in such a way as to make them indispensable for the application of
the standard.
In principle, the normative documents shall be International Standards published by ISO and/or IEC.
Normative documents published by other bodies may be listed provided that
— the document is recognized by the ISO and/or IEC committee concerned as having wide acceptance and
authoritative status as well as being publicly available,
— the ISO and/or IEC committee concerned has obtained the agreement of the authors or publishers (where
known) of the document to its inclusion,
— the authors or publishers (where known) have also agreed to inform the ISO and/or IEC committee
concerned of their intention to revise the document and of the points the revision will concern, and
— the ISO and/or IEC committee concerned undertakes to review the situation in the light of any changes in
the referenced document.
Type 3 Technical Reports are not permitted to contain normative matter, and shall not contain “normative
references”. They may, however, contain “references”.
— documents which have merely served as references in the preparation of the standard.
For dated references, each shall be given with its year of publication, or, in the case of enquiry or final drafts,
with a dash together with a footnote “To be published.”, and full title. Subsequent amendments to, or revisions
of, dated references will need to be incorporated by amendment of the standard referring to them. References
to specific divisions or subdivisions, tables and figures of another document shall always be dated.
Undated references may be made only to a complete document or a part thereof and only in the following
cases:
a) if it is accepted that it will be possible to use all future changes of the document referred to for the
purposes of the referring standard;
Undated references shall be understood to include all amendments to and revisions of the quoted publication.
The year of publication or dash shall not be given for undated references. When an undated reference is to all
parts of a standard, the publication number shall be followed by the indication “(all parts)” and the general title
of the series of parts (i.e. the introductory and main elements).
For the purposes of this part of ISO 18000, the following terms and definitions apply /the terms and definitions
given in … and the following apply.
4.1
term
text of the definition
The Terms and definitions clause is an optional element giving definitions necessary for the understanding
of certain terms used in the standard.
The term and definition list is introduced by a standard wording, which shall be modified as appropriate.
Rules for the drafting and presentation of terms and definitions are given in the ISO/IEC Directives, Part 3,
1997[2], annex C, and in ISO 10241[3].
A paragraph.
The Symbols (and abbreviated terms) clause is an optional element giving a list of the symbols and
abbreviated terms necessary for the understanding of the standard.
Unless there is a need to list symbols in a specific order to reflect technical criteria, all symbols should be listed
in alphabetical order in the following sequence:
— upper case Latin letter followed by lower case Latin letter (A, a, B, b, etc.);
— letters without indices preceding letters with indices, and with letter indices preceding numerical ones (B,
b, C, Cm, C2, c, d, d ext, d int, d 1, etc.);
6 Summary Of Commands
Note: G denotes the commands that require 2 single pulses (known as guard pulses) before they will execute.
Commands specific to a tag manufacturer will be accommodated by defining a Proprietary Command. This is
a command whose first symbol is a quadruple pulse. These codes, identified below, are reserved for individual
manufacturers of Tags and Readers to incorporate proprietary functionality, such as to facilitate programming
and testing of tags during the manufacturing process.
(Q = quad pulse)
There are three types of Read modes. Multiple Tag Read is the predominate mode of operation and is
described in detail in section 9.2. Other modes are Single Bit Read and Multiple Bit Read.
Some commands will perform a Single Bit Read of an associated Flag. Two Frame Pulses issued by the
reader are required, with the Tag responding after the first Frame Pulse to convey a logic “1”, and after the
second Frame Pulse to convey a logic “0”. There is also a specialized version used following Erase and Write
commands where there may be a response in both the First and Second frames.
Some commands will read the contents of registers, either 8 bits or 16 bits at a time. Two Frame Pulses
(comprising a Frame Pair) issued by the Reader are required for each bit of data read, and for each CRC and
Parity bit (calculated by the chip and transmitted following the data). A logic “1” is conveyed by the tag sending
a pulse in the first frame of the Frame Pair, and a logic “0” by a pulse in the second frame of the Frame Pair.
7 Architectural Notes
7.1 ID_FLAG
Used to indicate that either the tag has been identified, or that it has been eliminated from the multi-tag read
operation.
7.2 PRE_SEL_FLAG
7.3 VDDW_OK
Indicates that there was sufficient voltage to Program memory successfully. The VDDW_OK FLAG will be
cleared upon any successful WRITE, ERASE, or INITIALIZE MEMORY command.
Assuming 16 bit address space. Most commands dealing with tag memory will operate on the word pointed to
by this register. Address is memory location of 32 bit words
Bit 1 PRE_SEL_FLAG
Bit 3 CRC_ERR_FLAG
Bit 4 RESERVED
Bit 5 RESERVED
Bit 6 RESERVED
Bit 7 RESERVED
7.6 Parameters
Any command which includes parameters also includes an 8-bit CRC, which is calculated over the parameter
only. An overall odd parity bit covers the 6 bit command code, its parity bit, parameters and CRC. If an
incorrect CRC is received by the chip, the CRC_ERR_FLAG shall be set (or cleared if a good CRC is
received). Except where explicitly noted, a bad CRC or Parity will cause the chip to sleep.
This is used with reader commands that have a parameter field and is used with every 32 bit word returned
8 2
from the tag. Generating polynomial X + X + X + 1. The initial register value is 0x00. The code word is
shifted most significant bit first. Before transmitting, but after calculating, the syndrome byte is XOR’d with
0x55. Upon receipt, the syndrome byte is XOR’d with 0x55 before being shifted in to the CRC checker.
2 --- 0x 22 0x 99 0x 80 0x 35 0x 4c 0x19
Notes:
Example 1 is what the reader would transmit to the tag to execute a write command, data = 0x01020304
Example 2 is what the reader would receive during a continuation phase, tag data = 0x22998035
Example 3 illustrates why the XOR 0x55 is used (for noise immunity).
Example 5 is what the reader would transmit to the tag to execute a Start Multi-Tag-Read at address 0x000f
Cmd P
8 Block Diagrams
STATUS REGISTER
ID_FLAG
PRE_SEL_FLAG
VDD_OK
CRC_ERR
MUX
TAG MEMORY/
CRC LOGIC
SERIAL DATA IN
CONTROL LOGIC
Antenna
Circulator
Amplify/Filter/Detec
System Microprocessor t
Quadrature
Downconverter
Clock (Baseband )
Voltage Rectifier
and Antenna
Backscatter
Switch
(Baseband )
Control Filter
Power
Digital Circuitry
Supply
Tag
Antenna Switch Tag Transmits
Data Using
RS232 Antenna
Interface Backscatter
9 Command Descriptions
9.1 Wake_up
• Wake_up is a command.
• Sleep is a tag state.
When the tag is first illuminated, it will always be in the sleep state. When in the sleep state, tags will only
execute commands that include a waking action. Flags can not be changed while the tag is asleep. Once
awake, the tag will execute all commands. The Wake commands are guarded from execution during a data
sequence by the requirement that 2 single pulses must precede them.
Wakes all tags and performs a single bit read of the ID_flag. If its ID_FLAG is set, the tag will go to sleep after
reporting its state. Used in multi-tag read operations.
Uses binary tree process of elimination to force all but one tag to sleep. The reader will have learned the tag
identity. The reader may then conduct transactions with this single tag. Such transactions include reading of
more data, changing status of tag, and changing contents of memory that is not write protected. Once the tag
has been isolated in this manner and transactions have been completed, the ID_FLAG is set by the reader to
prevent the tag from participating in subsequent search of the binary tree. A simplified example is provided
later in this document.
A single command begins a multiple tag, multiple word read from tags that are awake. The multi-tag read
commands contain information specifying the address of the word to be processed. One type begins at the
location pointed to by the address register, while two other commands start at a fixed address.
After the Start Phase, the reader will issue a ‘separator,’ which is a double (data ‘0’) pulse. The separator
signals the tag to send its bit-31 content. The separator is followed by a string of double (data ‘0’) and triple
(data ‘1’) pulses according to the search branch being followed. As each 32-bit word + 8 bit CRC + 1 bit parity
has been stepped through, the tag automatically prepares to send the data at the subsequent (N + 1) address.
If the tag receives a separator at this boundary, it continues with the next word. If the tag receives a single
pulse at this boundary, it stays awake and awaits a subsequent command.
In normal mode, a tag will put itself to sleep if the pulse group from the reader (data ‘0’ or data ‘1’) does not
match the contents of its bit at that location. In Instant Elimination Mode, a single pulse is issued during the
Continuation Phase (any time between the separator and the first CRC bit, depending on which bits of the
data word are of interest) of the command. In this mode, the tag will not only go to sleep if it doesn’t match the
subsequent reader-sent bit, but will also set its own ID_FLAG. Instant Elimination Mode is used to quickly
eliminate tags so others can be pre-selected or otherwise processed. A second single pulse (before the first
CRC frame) puts the tag back into normal mode.
Starting at address 0, send the value of the bits in the location specified in the parameter for each of 32
contiguous addresses, followed by a valid CRC and parity. If one or more, but less than 32 contiguous word
addresses exist, send 0s for the nonexistent addresses and a valid CRC and Parity. The reader will issue
continuations to read subsequent groups of 32 words. If no valid addresses exist, the tag sends back 32 0's
AND a CRC of 00000000, parity of 1 but does not go to sleep. The reader will then stop issuing continuations.
If the bit location given by the parameter exceeds the total bit length of the word, the tag shall sleep. Valid bit
locations are bit 0 (MSB) through bit 40 (Write Protect), including the stored CRC bits.
9.3 Sleep_if
Tags are selectively put to sleep during Pre-select and Multi-tag-read to remove them from the binary search
process.
Reader is able to set and clear these flags to change the tag state and uses this to implement Pre-select and
Multi-tag-read. Each Set and Clear command is followed by two single pulses, constituting a single-bit read of
the respective Flag.
Returns the write protect state of the word pointed to by the address register.
9.6 Erase
Erases a variable length block. After the command and parameter, CRC and Parity, the reader will wait for 10
ms, then send a pulse doublet then a single pulse. After a pause of two frame intervals, reader issues two
single pulses which constitute a Specialized Read of the Write Protect status and VDD_OK flag.
Permanently prevents word from being erased or written to. The reader will wait for 20 ms, then send a pulse
doublet then a single pulse. After a pause of two frame intervals, reader issues two single pulses which
constitute a specialized read of the Write Protect Bit and VDD_OK flag.
Writes 32 bits of Data and 8 bits CRC to a single word in tag memory. After the last (parity) bit of the data
parameter, the reader will wait 20 ms, then send a pulse doublet then a single pulse. After a pause of two
frame intervals, reader issues two single pulses which constitute a specialized read of the Write Protect Bit
and VDD_OK flag.
Returns contents of 16-bit address register. Appends 8-bit CRC + odd parity.
Returns contents of 8-bit address register. Appends 8-bit CRC + odd parity.
Most significant byte of 16-bit address sent first, followed by LSB, then 8-bit CRC + odd parity. Attempting to
load an Address value exceeding the available memory will cause the chip enter the Sleep state.
These commands are preceded by a quad pulse and are to be defined by the individual manufacturers.
10 Application Notes
Generalized Multi-
Tag-Read flow
LIST_ID
Multi-tag-read 1 word
(increment tag address)
No
word count
= 0?
Yes
set ID_FLAG
The ability to identify all tags in the RF field, as well as to isolate one or more of many tags for reading or
writing, is generically known as ‘multi-tag read capability.’ Multi-tag read capability is accomplished by taking
advantage of various states and flags to successively eliminate unwanted tags from communication with the
reader. Specifically, tag memory data is examined one bit at a time, and a binary string is traversed. By the
time the end node of the traversal is reached, only one tag (if its data are unique) or a number of tags (if their
data are identical) are left in the ‘awake’ state. All other tags are ‘asleep.’ The length of the binary string
traversal can be any multiple of 32 bits, up to the length of the entire tag memory contents.
This example uses the tag’s ID_FLAG to mark tags that have already been identified or otherwise processed.
It uses the ‘sleep’ state to prevent tags from interfering with the communication between the reader and
desired tags. In the example, the two-word (64-bit) unique identifier that is factory programmed into each tag is
traversed. In this case, one and only one tag will be left awake at the end. This tag could then be written to or
read from with no interference from other tags in the field. However, this algorithm can be used on any block
of tag memory.
2. If there is a tag response in second half or both halves of the one-bit frame pair, there is a tag that has not
yet been identified: go to next step. Otherwise, wait for a new, unidentified tag to come into the field by
repeating the previous step.
3. Issue the Start Multi-Tag-Read with address field = 0 command (ref 4). This will eliminate (put to sleep)
most of the tags in the field after the first 32 bit word. If there are tags with duplicate data in this word, there
may still be more than one tag awake at this point. The multi-read command is continued into the next word
and will select one tag, assuming 64-bit unique data (unique serial numbers).
4. Issue the Set ID_FLAG command (ref 12), loop back to step 1.
The Multi-Tag-Read command relies on intelligence designed into the tag to make the decisions on if and
when to drop out of a Multi-Tag-Read sequence. Decisions are based on the tags’ previous actions and the
reader’s single-bit replies to the tags’ responses during the bit-by-bit interrogation process.
1. The reader sends the tag one of its Start Multi-Tag-Read commands (ref 3, 4, or 5) and Address
Parameter if required.
2. The reader then sends a pulse doublet.. This is known as the ‘separator’. Immediately after the separator,
the reader looks for a tag response. If the reader gets a pulse, at least one tag had bit 31 set (logic 1) at that
memory location.
3. If the reader receives a tag generated pulse, the reader sends a data pulse triplet (logic 1) as the next
symbol, in effect echoing the response of the tag. If the reader does not receive a pulse from the tag, the
reader sends a data pulse doublet (logic 0) as the next symbol.
4. If the tag receives a data pulse triplet (logic 1) from the reader, but did not respond to the last data pulse,
the tag has failed this isolation round and goes to sleep. This continues until the reader has sent data pulses
bits 31 down to 0 of the word selected.
5. After the tag has responded to the 32 data queries from the receiver, the tag will send an 8-bit CRC in the
following way:
a) Respond if the first bit of the calculated CRC across the 32 data bits is a ‘1’, or
c) The reader and tag then continue in lockstep for the remaining 7 bits of CRC, and one more for odd parity.
Just as during the data phase, the tag will sleep if the reader does not echo the tag’s response.
6. To continue to the next word, the reader issues a separator. The tag will respond if bit 31 of this next word
is set.
7. If, instead of a separator, the tag receives a single pulse, it terminates the auto-increment mode and
awaits another command.
If the user wants to quickly eliminate tags with certain contents without identifying them, the reader can cause
the tag to enter Instant Elimination mode. This causes the tag to set its own ID_FLAG at the time it goes to
sleep during the continuation phase. On subsequent MTR operations, the tag will not participate. To put a tag
into Instant Elimination mode, a single pulse is issued any time after the separator, but before the frame
corresponding to bit 0 of the data word. If a second single pulse is issued during the continuation phase, the
tag reverts to non-Instant Elimination mode.
Note: The “parity bit” shown is the last bit of the string of bits for the command sent by the reader
1. Multi-tag read commands, Reference 3, 4, 5, always send a separator pulse (data zero) after the
command parity bit. Tags with left most bit set (logic 1) will send a pulse back to the reader.
2. Read flag commands, Reference 16, 17, 18, 19, always send two single pulses, spaced by frame period,
after the parity bit.
a. Tags with flag set (logic 1) will respond after the first pulse.
b. Tags whose flag is clear (logic 0) will respond after the second pulse
a. Tags send a pulse back to the reader if the tag bit is set (logic 1)
b. Tags do not send a pulse back to the reader if the tag bit is clear (logic 0)
a. Reader sends a data pulse one (three pulses) if a tag response was received
b. Reader sends a data pulse zero (two pulses) if there was no tag response.
5. The tag goes to sleep if the tag bit does not match the data pulse from the reader.
6. The tag decrements its counter if the tag bit matches the data pulse from the reader.
Standard Multi-Tag-Read
Single-bit Read
Parity bit
1. Reader sends Wake_up command (Ref 2). The command includes two pulses after the parity bit.
Since ID flags are not set (logic 0), all tags respond with a return pulse after the second single pulse and stay
awake
If one of the tags would have had the ID flag set, it would have responded with a return pulse after the first
single pulse and would have gone to sleep.
Reader then sends the separator pulse pair (this is same as the data zero pulse pair)
The binary tree traverse starts from the left in this case.
no response
3. Reader sends a one since last tag response indicates at least one tag was present with a logic 1 in the
leftmost bit. Thus the reader echoed the response of a tag or tags.
4. Since tag 2’s left most bit is zero, the tag interprets the logic one data as the direction to go to sleep. Tag
2 goes to sleep and does not respond during the search of the right hand bits.
Since tags 1 and 3 both have a 1 in bit 3, they increment their counters to be ready for decisions on bit 2.
5. Since tags 1 and 3 both have a 0 in bit 2, they do not respond to the reader’s logic one.
no response
no response no response
6. The reader did not receive a response to the last data one pulse group.
The reader then issues a data zero pulse group. The reader echoed the tag reaction.
Since tags have a 0 in bit 2, which matches the data zero group sent by the reader, they advance their
counters to bit 1.
7. The reader did not receive a response to the last data zero pulse group.
The reader then issues a data zero pulse group. The reader echoed the tag reaction.
Since tags have a 0 in bit 1, which matches the data zero group sent by the reader, they advance their
counters to bit 0.
no response no response
no response no response
8. Since tag 3 has bit zero set, tag three responds with a pulse.
Tag 1, since it does not have bit zero set goes to sleep.
9. This picture shows the values of the last four data pulse sets that were sent.
10. A command to “Set ID_FLAG” would typically be sent to the remaining tag. Reader would send a “Wake”
command.
Single-bit Read
Parity bit
11. Reader sends Wake, Read ID_FLAG, sleep if set command, Reference 2.
Tag 3 has the ID_FLAG set and responds after the first pulse.
The ID_Flag for Tags 1 & 2 are not set and they respond after the second pulse.
The process then goes back to step 1 and is repeated until another tag is identified.
The process then goes back to step 1 and is repeated until the third tag is identified.
13. Reader sends Wake, Read ID_FLAG, sleep if set command, Reference 2. Reader gets a response only
after its first single pulse. Since there is no response after its second single pulse, the reader recognizes that
there are no tags remaining in the field that have not been identified.
The reader in the general case would continue to issue the Wake, Read ID_FLAG. When a response is
received after the second pulse, reader would issue a Start Multi-Tag read and repeat the process for each of
the tags encountered.
The reader does not issue Start Multi-Tag Read commands when there is no response to the Wake, Read
ID_FLAG command.
5 4 3 2 1 0 P 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
cmd.
command code address value
parity
7 6 5 4 3 2 1 0 P 31 30 29 28 27 26 25 24 23 22
tag responses
21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 P
tag data CRC:
0x7f
data
data CRC
parity
tag data parity:
Single pulse
ends command 1
MTR data portion (continued)
2. If there is a tag response in the second or both halves of the one-bit frame pair, there is a tag that has not
yet been identified/selected: go to next step. Otherwise, wait for a new, unidentified tag to come into the field
by repeating previous the previous step.
3. Issue Start Multi-Tag-Read command, with address (Ref 28) Normally, the reader would follow a search
tree, with the order depending on the leftmost bit that is set. In this case though, when the reader reaches the
frame that corresponds to the first bit of the pre-select field, it will issue a single frame pulse. This signals the
tags that if they do not have the next-sent value in that bit position, they are to set their ID_FLAG immediately
(Instant Elimination mode) and go to sleep. For example, if we are at bit position 27, and we want to pre-select
tags with bit 27 set, the reader will send a single pulse followed by a triple (data ‘1’). Any tag that doesn’t have
a ‘1’ in bit 27 will go to sleep and set its own ID_FLAG. Tags with ID_FLAG set will not participate in
subsequent Multi-Tag-Read commands. Since this is the only bit pre-selected, send another single pulse to
revert to standard Multi-Tag-Read operation.
Note 1: if the field of interest starts at bit 31 (uppermost bit) of the first word, then the separator must be a
followed by a single pulse.
Note 2: More than 1 bit can be pre-selected. Just don’t issue the second single pulse until the field of interest
is completed (see example below).
Note 3: To enter Instant Elimination Mode at a word boundary in the midst of a multiple word read, issue a
single pulse after the separator.
If this is the last word of a multiple word read, issue a single pulse.
Parity bit
5. Tag 1 does not have a '1' in next bit (bit2), tag 1 tag 2 tag 3
so it goes to sleep and sets its own ID_FLAG. 1000 0100 1101
ID
no response
no response
8. Tag 3 has a '1' in bit 0, so it
stays awake. Interrogator responds tag 1 tag 2 tag 3
with a '1', tag 3 sets its 1000 0100 1101
own ID_FLAG ID ID
Single-bit Read
Parity bit
tag 1 tag 3
tag 2 1101
1000
0100 ID
ID
PRE
no response
no response
no response no response
tag 1 tag 2 tag 3
1000 0100 1101
ID ID
PRE
no response no response
no response
tag 3
15. Interrogator forces a data '0' in bit 1. tag 1 tag 2
1101
Tag doesn't respond, stays awake. 1000 0100 ID
ID PRE
no response no response
no response
16. This is the end of the select field, so Interrogator issues a single pulse to exit Instant Elimination Mode. It
then sends a zero (because there was no tag response).
Tag 2 doesn't respond, and stays awake. Interrogator sends a '0' to complete the
tag response
Command
Parity bit Separator
10.6.2 Two-word response: word 1, bits (2 down to 0), word 2 bits (31 down to 30)
Command
Parity bit Separator
data mismatch in this region puts tag to sleep. ID_FLAG will not be set in this case.
Heavy line: instant elimination mode
tag response
tag response
Heavy line: instant elimination mode
tag response
Following is an example showing how to use this command set to avoid having to read an entire 128-bit
identity field for every tag in the RF field. The application in this case has chosen to put the identity field in
words 3,4,5 and 6 (128/32 = 4 32-bit words). The example uses three different identity types of tags. For this
example there are 3 tags in each group.
Every single tag in the field has a unique factory-written serial number in words 0 and 1.
The data that are wanted reside in address 13 of the group A tags and address 14 of the group B
tags. The data in group C tags are unwanted.
128-bit ID example
Start
No are any
ID_FLAGS
zero?
Yes
Start Multi-Tag-Read
Address = 3
(ref 3)
Address 3
data = 0x33333333
continue
Address 4
data = 0x33333333
continue
Address 5
data = 0x33333333
continue
Address 6
data = 0x33333333
128-bit ID = 0x33333333333333333333333333333333
No are any
ID_FLAGS
zero?
Yes
Start Multi-Tag-Read
Address = 3
(ref 3)
Address 3
data = 0x22222222
continue
Address 4
data = 0x22222222
continue
Address 5
data = 0x22222222
continue
Address 6
data = 0x22222222
128-bit ID = 0x22222222222222222222222222222222
Set PRE_SEL_FLAG
(ref 14)
Read PRE_SEL_FLAG,
Sleep if Clear (ref 18)
are any No
PRE_SEL_FLAGs
set?
Yes
Now reader isolates
each group B tag in turn
Start Multi-Tag-Read
at Address 0 (ref 4)
Address 0
pass 1: data = 0x00000006
pass 2: data = 0x00000005
pass 3: data = 0x00000004
continue
Address 1
pass 1: data = 0x00000006, Unique ID = 0x0000000600000006
pass 2: data = 0x00000005, Unique ID = 0x0000000500000005
pass 3: data = 0x00000004, Unique ID = 0x0000000400000004
Start Multi-Tag-Read
Address = 14
(ref 3)
3
Standard Wake
(ref 1)
Clear PRE_SELECT_FLAG
(ref 15)
Start Multi-Tag-Read
Address = 3
(ref 3)
Address 3
data = 0x11111111
continue
Address 4
data = 0x11111111
continue
Address 5
data = 0x11111111
continue
Address 6
data = 0x11111111
128-bit ID = 0x11111111111111111111111111111111
Set PRE_SEL_FLAG
(ref 14)
Read PRE_SEL_FLAG,
Sleep if Clear (ref 18)
are any No
PRE_SEL_FLAGs
set?
Yes
Now host isolates
each group A tag in turn
Start Multi-Tag-Read
at address 0 Address 0
(ref 4)
continue Address 2
Start Multi-Tag-Read
Address = 13 Host wants the data in address 13
(ref 3)
Yes
are any
ID_FLAGS
zero?
No
END
command
command Bit 0 command Bit 1 command Bit 5 data bit 0 data bit 1
parity bit
data bit 30 data bit 31 data CRC bit 32 data CRC bit 33 data CRC bit 39 data parity bit
20 mS delay
11 Signal Specification
The purpose of this clause is to specify the parameters of an RFID tag. The timing of the tag
(envelope of the RF signal) described in Figure 11- 1 illustrates a transmitted pulse and the
reflected pulse. Timing parameters are specified in
Tin_width Tin_gap
Tml
Vin_drop Tml_width
Reflected
Transmitted
Tin_width Tin_gap
Tml
Vin_drop Tml_width
Reflected
Transmitted
Tml 1st
Tml 2nd
Tml 3rd
Reflected
Transmitted
• As specified in Table 11-2, the tag will respond with three pulses unless interrupted by a transmitted signal
from the reader. A signal from the reader following the tag’s first pulse but before the second pulse is to occur
nd rd
will cause the tag to not respond with the 2 and 3 return pulses. Likewise, a signal from the reader following
rd
the tag’s second pulse but before the third pulse is to occur will cause the tag to not respond with the 3 return
pulse.
12 Summary
The attributes of the system are not always readily apparent based on the above-described technical
description. In an effort to better convey the advantages of the system, a summary is presented below:
• Assuming that transmission from the reader to the tag is mandatory for optimized system operation, it is
imperative to reduce the transmitted side band. To that end, the reduced modulation Sinusoidal profile offers
the least amount of side band spectrum.
• The short sets of reduced power transmission used to encode information from the reader to the tag
allows for easy implementation in both the reader and the tag. The silicon area of the RFID chip is minimized
as well as the power required to sense the incoming signal. In addition, since the power lapse to the tag is less
than 2 microseconds, the on-chip capacitance is minimized thus reducing chip area and cost.
• The return signal from the tag to the reader is easily distinguished from the transmit signal and is readily
detectable by the reader. Since the time at which the backscattered signal is known to occur, the reader can
screen all noise outside the prescribed “window”. Also, detection of either edge of the return signal is
acceptable negating the need to detect both edges with more expensive reader sensing techniques.
• Errors in the signals returned to the readers can be detected in real time through the CRC associated with
each individual word.
• The modulation technique allows for systems to be “synchronized” so that many readers can be operated
in close proximity. By having all readers in an area transmit at the same time, then waiting for tags to respond
before transmitting the subsequent bit, the readers will not interfere with each other.
• The communication protocol along with the extensive command structure allows for a very flexible system
capable of meeting the various customer requirements. Reads of individual words or blocks, class sorts, tag
identification, and many other capabilities are all possible but not at the expense of degrading system
performance.
• The multi read technique allows for reading any number of tags in the field. It is the only algorithm that is
not probabilistic and results in the total time to read multiple tags to vary linearly with the number of tags. In
addition, the technique by its nature does not suffer from tags entering and exiting the field.
• The multi read technique also allows for class sorting “on the fly”. A specific code identifier placed in any
section of the memory can be used to direct the reader in searching for specific classes. Again, all is under
software control.
• The air interface allows for codes beyond binary to be transmitted. This allows for a more efficient method
(shorter amount of time) of transmitting information.