Source: http://www.google.com/patents/US8072327?dq=5,646,839
Timestamp: 2017-07-22 11:12:02
Document Index: 395075877

Matched Legal Cases: ['Application No. 60', 'Application No. 61', 'art 700', 'art 700', 'art 700', 'art 700', 'art 700', 'art 700', 'art 700', 'art 1200', 'art 1200', 'art 700', 'art 1200', 'art 1200', 'art 1200']

Patent US8072327 - Causing RFID tags to reply using changed reply timing - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsRFID reader systems, readers, components, software and methods cause RFID tags to reply using changed reply timing. In a number of embodiments, this timing change is achieved by causing a custom timing command to be transmitted to a tag. In some embodiments, the changed reply timing affects an amount...http://www.google.com/patents/US8072327?utm_source=gb-gplus-sharePatent US8072327 - Causing RFID tags to reply using changed reply timingAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS8072327 B2Publication typeGrantApplication numberUS 12/035,397Publication dateDec 6, 2011Filing dateFeb 21, 2008Priority dateFeb 21, 2007Fee statusPaidAlso published asUS7999675, US20080197978, US20080197979Publication number035397, 12035397, US 8072327 B2, US 8072327B2, US-B2-8072327, US8072327 B2, US8072327B2InventorsArthur Gustav Enyedy, Christopher J. Diorio, Gregory T. KavounasOriginal AssigneeImpinj, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (20), Non-Patent Citations (4), Referenced by (3), Classifications (8), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetCausing RFID tags to reply using changed reply timing
US 8072327 B2Abstract
RFID reader systems, readers, components, software and methods cause RFID tags to reply using changed reply timing. In a number of embodiments, this timing change is achieved by causing a custom timing command to be transmitted to a tag. In some embodiments, the changed reply timing affects an amount of delay before a tag backscatters a reply.
1. A component for a Radio Frequency Identification (RFID) reader to communicate with an RFID tag, the tag having received a first command, and backscattered a first reply encoding a functional content responsive to the first command, the first reply using a first delay before the tag starts backscattering the first reply after receiving the first command, comprising:
an operational processing block for causing to be transmitted to the tag a custom timing command, the tag then backscattering a second reply that encodes the same functional content as the first reply, the second reply using a second delay before the tag starts backscattering the second reply after receiving a most recent command prior to backscattering the second reply, the second delay different from the first delay responsive to receiving the custom timing command, in which
if the tag was in a disabled state when it received the custom timing command then the second delay would be the same as the first delay,
if the tag was in an enabled state when it received the custom timing command then the second delay would be different from the first delay, and
an Enable command transmitted while the tag is in the disabled state causes the tag to transition to the enabled state.
2. The component of claim 1, in which
the second reply is identical to the first reply.
3. The component of claim 1, in which
the second reply includes at least one bit which is arranged similarly to those of the first reply.
4. The component of claim 1, in which
the functional content is one of a code stored in a memory, and a random number.
5. The component of claim 1, in which
the tag is caused to lose power after backscattering the first reply and before receiving the custom timing command.
6. The component of claim 1, in which
the tag is caused to not lose power after backscattering the first reply and before receiving the custom timing command.
7. The component of claim 1, in which
the first command is a command to identify,
the first reply is an identifying reply, and
in which the custom timing command is caused to be transmitted responsive to the identifying reply.
8. The component of claim 1, in which
the most recent command is the custom timing command.
9. The component of claim 1, in which
the most recent command is an intervening command transmitted after the custom timing command.
10. The component of claim 1, in which
a third command is caused to be transmitted to the tag after it has backscattered the second reply, the tag therefore backscattering a third reply using a third delay, the third delay different from the first delay responsive to having received the custom timing command.
11. The component of claim 10, in which
the third delay is substantially the same as the second delay.
12. The component of claim 1, in which
the tag is able to backscatter the second reply using the second delay regardless of what state it is in at the time it receives the custom timing command.
13. The component of claim 1, in which
a Disable command is caused to be transmitted to the tag while the tag is in the enabled state, so as to cause the tag to transition internally to the disabled state responsive to receiving the Disable command.
14. The component of claim 1, in which
a Tune command is caused to be transmitted to the tag, which encodes a time indicating parameter, and
the second delay is determined from the time-indicating parameter.
15. The component of claim 1, in which
the Tune command is one of the first command and the custom timing command.
16. An article comprising: a storage medium, the storage medium having instructions stored thereon, in which when the instructions are executed by at least an RFID reader system component for communicating with an RFID tag, the tag having received a first command, and backscattered a first reply encoding a functional content responsive to the first command, the first reply using a first delay before the tag starts backscattering the first reply after receiving the first command, the instructions result in actions comprising:
causing to be transmitted to the tag a custom timing command, the tag then backscattering a second reply that encodes the same functional content as the first reply, the second reply using a second delay before the tag starts backscattering the second reply after receiving a most recent command prior to backscattering the second reply, the second delay different from the first delay responsive to receiving the custom timing command, in which
17. A method for a Radio Frequency Identification (RFID) reader system component to communicate with an RFID tag, the tag having received a first command, and backscattered a first reply encoding a functional content responsive to the first command, the first reply using a first delay before the tag starts backscattering the first reply after receiving the first command, comprising:
18. The method of claim 17, in which
19. The method of claim 17, in which
20. The method of claim 17, in which
21. The method of claim 17, in which
This application claims priority from U.S. Provisional Application No. 60/902,745, filed on Feb. 21, 2007, the disclosure of which is hereby incorporated by reference for all purposes.
This application claims priority from U.S. Provisional Application No. 61/005,232 filed on Dec. 4, 2007, the disclosure of which is hereby incorporated by reference for all purposes.
This application may be found to be related to U.S. patent application Ser. No. 12,035,393 by the same inventors, titled “RFID TAGS REPLYING USING CHANGED REPLY TIMING”, filed by the same assignee on the same day as the instant application.
The present description is about Radio Frequency IDentification (RFID) systems, and more specifically for systems where RFID tags reply to readers using changed reply timing.
A tag that senses the interrogating RF wave responds by transmitting back another RF wave. The tag generates the transmitted back RF wave either originally, or by reflecting back a portion of the interrogating RF wave in a process known as backscatter. Backscatter may take place in a number of ways. In addition, tags usually have prescribed reply timings for replying by backscattering.
It is desired to have RFID systems with additional capabilities, for improved functionality.
Briefly, the present invention provides RFID reader systems, readers, components, software and methods for causing RFID tags to reply using changed reply timing. In a number of embodiments, this timing change is achieved by causing a custom timing command to be transmitted to a tag. In some embodiments, the changed reply timing affects an amount of delay before a tag backscatters a reply.
The present invention also provides RFID tags and chips for RFID tags that are capable of replying using changed reply timing. In a number of embodiments, this timing change is achieved when a tag receives a custom timing command from an RFID reader. In some embodiments, the changed reply timing affects an amount of delay before a tag backscatters a reply.
The invention offers the advantage that some tags can be processed differentially from others, which can improve the functionality of a whole RFID system that processes RFID-tagged items. Additionally, the fact that the tags can actually perform the feature can serve as a verification criterion that the tags are not counterfeit. Moreover, some embodiments can enhance the privacy of the owners of items tagged with such tags.
FIG. 5 is a block diagram of a whole RFID reader system according to embodiments.
FIG. 6 is a block diagram illustrating an overall architecture of an RFID reader system according to embodiments.
FIG. 7 is a flowchart illustrating methods for an RFID reader system component according to embodiments.
FIG. 8 is a diagram illustrating commands that may be transmitted as a result of operations of the flowchart of FIG. 7 according to embodiments.
FIG. 9A is a table illustrating the fields of the Select command of the Gen2 Spec version 1.1.0, versions of which may be used as any one or more of the commands of FIG. 8 according to embodiments.
FIG. 9B is a table illustrating how a number of custom commands can be enabled in a reader and a tag.
FIG. 9C is a table showing sample values that can be used for the table of FIG. 9B.
FIG. 10 is a block diagram of an implementation of an electrical circuit formed in an IC of the tag of FIG. 2.
FIG. 11 is an optional partial state diagram of a state machine of a tag having an electrical circuit as shown in FIG. 10.
FIG. 12 is a flowchart illustrating methods for a tag according to embodiments.
FIG. 13 is two timing diagrams for illustrating how a reply timing can be changed according to some embodiments.
FIG. 14 is a conceptual timing diagram for illustrating how an amount of delay in the reply timings of the embodiments of FIG. 13 can be further tuned.
One such protocol is called the Specification for RFID Air Interface—EPC(™) Radio-Frequency Identity Protocols Class-1 Generation-2 UHF RFID Protocol for Communications at 860 MHz-960 MHz, which is also colloquially known as “the Gen2 Spec”. The Gen2 Spec has been ratified by EPCglobal, which is an organization that maintains a website at: <http://www.epcglobalinc.org/> at the time this document is initially filed with the USPTO.
In addition, a protocol can be a variant of a stated specification such as the Gen2 Spec, for example including fewer or additional commands than the stated specification calls for, and so on. In such instances, additional commands are sometimes called custom commands.
FIG. 4 is a block diagram showing a detail of an RFID reader system 410, which can be the same as reader 110 shown in FIG. 1. A unit 420 is also known as a box 420, and has at least one antenna driver 430. In some embodiments it has four drivers 430. For each driver 430 there is an output device for a connector. The output device is typically a coaxial cable plug. Accordingly connectors 435 can be attached to the output devices of the provided respective drivers 430, and then connectors 435 can be attached to respective antennas 440.
A driver 430 can send to its respective antenna 440 a driving signal that is in the RF range, which is why connector 435 is typically but not necessarily a coaxial cable. The driving signal causes the antenna 440 to transmit an RF wave 412, which is analogous to RF wave 112 of FIG. 1. In addition, RF wave 426 can be backscattered from the RFID tags, analogous to RF wave 126 of FIG. 1. Backscattered RF wave 426 then ultimately becomes a signal sensed by unit 420.
Unit 420 also has other components 450, such as hardware and/or software and/or firmware, which may be described in more detail later in this document. Components 450 control drivers 430, and as such cause RF wave 412 to be transmitted, and the sensed backscattered RF wave 426 to be interpreted. Optionally and preferably there is a communication link 425 to other equipment, such as computers and the like, for remote operation of system 410.
FIG. 5 is a block diagram of a whole RFID reader system 500 according to embodiments. System 500 includes a local block 510, and optionally remote components 570. Local block 510 and remote components 570 can be implemented in any number of ways. It will be recognized that reader 110 of FIG. 1 is the same as local block 510, if remote components 570 are not provided. Alternately, reader 110 can be implemented instead by system 500, of which only the local block 510 is shown in FIG. 1. Plus, local block 510 can be unit 420 of FIG. 4.
Local block 510 is responsible for communicating with the tags. Local block 510 includes a block 551 of an antenna and a driver of the antenna for communicating with the tags. Some readers, like that shown in local block 510, contain a single antenna and driver. Some readers contain multiple antennas and drivers and a method to switch signals among them, including sometimes using different antennas for transmitting and for receiving. And some readers contain multiple antennas and drivers that can operate simultaneously. A demodulator/decoder block 553 demodulates and decodes backscattered waves received from the tags via antenna block 551. Modulator/encoder block 554 encodes and modulates an RF wave that is to be transmitted to the tags via antenna block 551.
Local block 510 additionally includes an optional local processor 556. Processor 556 may be implemented in any number of ways known in the art. Such ways include, by way of examples and not of limitation, digital and/or analog processors such as microprocessors and digital-signal processors (DSPs); controllers such as microcontrollers; software running in a machine such as a general purpose computer; programmable circuits such as Field Programmable Gate Arrays (FPGAs), Field-Programmable Analog Arrays (FPAAs), Programmable Logic Devices (PLDs), Application Specific Integrated Circuits (ASIC), any combination of one or more of these; and so on. In some cases some or all of the decoding function in block 553, the encoding function in block 554, or both, may be performed instead by processor 556.
Local block 510 additionally includes an optional local memory 557. Memory 557 may be implemented in any number of ways known in the art. Such ways include, by way of examples and not of limitation, nonvolatile memories (NVM), read-only memories (ROM), random access memories (RAM), any combination of one or more of these, and so on. Memory 557, if provided, can include programs for processor 556 to run, if provided.
In some embodiments, memory 557 stores data read from tags, or data to be written to tags, such as Electronic Product Codes (EPCs), Tag Identifiers (TIDs) and other data. Memory 557 can also include reference data that is to be compared to the EPC codes, instructions and/or rules for how to encode commands for the tags, modes for controlling antenna 551, and so on. In some of these embodiments, local memory 557 is provided as a database.
Some components of local block 510 typically treat the data as analog, such as the antenna/driver block 551. Other components such as memory 557 typically treat the data as digital. At some point there is a conversion between analog and digital. Based on where this conversion occurs, a whole reader may be characterized as “analog” or “digital”, but most readers contain a mix of analog and digital functionality.
If remote components 570 are indeed provided, they are coupled to local block 510 via an electronic communications network 580. Network 580 can be a Local Area Network (LAN), a Metropolitan Area Network (MAN), a Wide Area Network (WAN), a network of networks such as the internet, or a mere local communication link, such as a USB, PCI, and so on. In turn, local block 510 then includes a local network connection 559 for communicating with network 580.
There can be one or more remote component(s) 570. If more than one, they can be located at the same location, or in different locations. They can access each other and local block 510 via network 580, or via other similar networks, and so on. Accordingly, remote component(s) 570 can use respective remote network connections. Only one such remote network connection 579 is shown, which is similar to local network connection 559, etc.
Remote component(s) 570 can also include a remote processor 576. Processor 576 can be made in any way known in the art, such as was described with reference to local processor 556.
Remote component(s) 570 can also include a remote memory 577. Memory 577 can be made in any way known in the art, such as was described with reference to local memory 557. Memory 577 may include a local database, and a different database of a Standards Organization, such as one that can reference EPCs.
Of the above-described elements, it is advantageous to consider a combination of these components, designated as operational processing block 590. Block 590 includes those that are provided of the following: local processor 556, remote processor 576, local network connection 559, remote network connection 579, and by extension an applicable portion of network 580 that links connection 559 with connection 579. The portion can be dynamically changeable, etc. In addition, block 590 can receive and decode RF waves received via antenna 551, and cause antenna 551 to transmit RF waves according to what it has processed.
Block 590 includes either local processor 556, or remote processor 576, or both. If both are provided, remote processor 576 can be made such that it operates in a way complementary with that of local processor 556. In fact, the two can cooperate. It will be appreciated that block 590, as defined this way, is in communication with both local memory 557 and remote memory 577, if both are present.
Accordingly, block 590 is location agnostic, in that its functions can be implemented either by local processor 556, or by remote processor 576, or by a combination of both. Some of these functions are preferably implemented by local processor 556, and some by remote processor 576. Block 590 accesses local memory 557, or remote memory 577, or both for storing and/or retrieving data.
Reader system 500 operates by block 590 generating communications for RFID tags. These communications are ultimately transmitted by antenna block 551, with modulator/encoder block 554 encoding and modulating the information on an RF wave. Then data is received from the tags via antenna block 551, demodulated and decoded by demodulator/decoder block 553, and processed by processing block 590.
FIG. 6 is a block diagram illustrating an overall architecture of an RFID reader system 600 according to embodiments. It will be appreciated that system 600 is considered subdivided into modules or components. Each of these modules may be implemented by itself, or in combination with others. It will be recognized that some aspects are parallel with those of FIG. 7. In addition, some of them may be present more than once.
RFID reader system 600 includes one or more antennas 610, and an RF Front End 620, for interfacing with antenna(s) 610. These can be made as described above. In addition, Front End 620 typically includes analog components.
System 600 also includes a Signal Processing module 630. In this embodiment, module 630 exchanges waveforms with Front End 620, such as I and Q waveform pairs. In some embodiments, signal processing module 630 is implemented by itself in an FPGA.
System 600 also includes a Physical Driver module 640, which is also known as Data Link. In this embodiment, module 640 exchanges bits with module 630. Data Link 640 can be the stage associated with framing of data. In one embodiment, module 640 is implemented by a Digital Signal Processor.
System 600 additionally includes a Media Access Control module 650, which is also known as MAC layer. In this embodiment, module 650 exchanges packets of bits with module 640. MAC layer 650 can be the stage for making decisions for sharing the medium of wireless communication, which in this case is the air interface. Sharing can be between reader system 600 and tags, or between system 600 with another reader, or between tags, or a combination. In one embodiment, module 650 is implemented by a Digital Signal Processor.
System 600 moreover includes an Application Programming Interface module 660, which is also known as API, Modem API, and MAPI. In some embodiments, module 660 is itself an interface for a user.
All of these functionalities can be supported by one or more processors. One of these processors can be considered a host processor. Such a processor would, for example, exchange signals with MAC layer 650 via module 660. In some embodiments, the processor can include applications for system 600. In some embodiments, the processor is not considered as a separate module, but one that includes some of the above-mentioned modules of system 600.
A user interface 680 may be coupled to API 660. User interface 680 can be manual, automatic, or both. It can be supported by a separate processor than the above mentioned processor, or implemented on it.
It will be observed that the modules of system 600 form something of a chain. Adjacent modules in the chain can be coupled by the appropriate instrumentalities for exchanging signals. These instrumentalities include conductors, buses, interfaces, and so on. These instrumentalities can be local, e.g. to connect modules that are physically close to each other, or over a network, for remote communication.
The chain is used in opposite directions for receiving and transmitting. In a receiving mode, wireless waves are received by antenna(s) 610 as signals, which are in turn processed successively by the various modules in the chain. Processing can terminate in any one of the modules. In a transmitting mode, initiation can be in any one of these modules. Ultimately, signals are transmitted internally, for antenna(s) 610 to transmit as wireless waves.
The architecture of system 600 is presented for purposes of explanation, and not of limitation. Its particular subdivision into modules need not be followed for creating embodiments according to the invention. Furthermore, the features of the invention can be performed either within a single one of the modules, or by a combination of them.
Methods are now described more particularly according to embodiments. Such methods may be practiced by different embodiments, including but not limited to RFID reader system components as described above. In addition, individual operations of such methods may be practiced by different readers, at different phases of the lifetime of an RFID tag, with or without interruptions between them, and so on.
In some embodiments, a first command is caused to be transmitted to the RFID tag. The first command is of course encoded in an electromagnetic wave such as wave 112, according to a communication protocol. Such protocols specify a number of such commands, and any such command can be considered to be the first command. Such commands can include, for example, command requesting a handle, such as a random number, or a more identifying number such as a TID or an EPC. A number of additional possible first commands are also described below in more detail, but that is only for example and not for limitation.
In some embodiments, a backscattered first reply is received from the tag, responsive to the first command having been transmitted. A reply to the first command can be considered as the first reply for purposes of this document. The first reply uses a first reply timing as the reply timing, and such tag reply timings are described in more detail later in this document.
The first command can be sent to a tag that has been singulated from a tag population. In other instances, the tag has not yet been singulated.
In one class of examples, the first command can be any of the commands issued in an exchange for commissioning a tag, where data is written in its memory, and an acknowledging reply is backscattered. It is known, therefore, that a tag that has been commissioned has received such a first command, and has replied to it.
FIG. 7 is flowchart 700 for illustrating some methods according to embodiments. In some embodiments, at optional operation 710 of FIG. 7, the first command is a command for the tag to identify itself to the reader. In some instances, operation 710 can be used for identifying the tag, and therefore knowing that it is capable of replying using a changed reply timing, as described in the present document. If operation 710 is not performed, however, the first command can be considered any other command in the exchange.
In some embodiments, at optional operation 720, an identifying reply is received as the first reply. These embodiments are preferably where the first command is operation 710. Again, if operation 720 is not performed, the first reply can be considered any other reply that a reader has done with a tag.
Operation 770 of flowchart 700 is now described. While the description of operation 770 is somewhat out of turn for the flow of flowchart 700, it is presented at this point in the document so that the description of the additional optional operations of flowchart 700 taking place before operation 770 will make sense.
At operation 770, a custom timing command is caused to be transmitted to the tag, after receiving the first reply. In response to receiving the custom timing command, when the tag later backscatters a second reply, that second reply uses a second reply timing that is different from the first reply timing. Again, examples of such second replies and such second reply timings are described in more detail later in this document.
It will be appreciated that operation 770 may be performed either by the same reader as the one that transmitted the first command, or by a different reader. In either case, the tag may or may not have lost power after backscattering the first reply, and before receiving the custom timing command. In embodiments where a reader processes a tag that has already been commissioned, operation 770 takes place. In addition, a first command may or may not have been transmitted. If it has been, then it may or may not be operation 710.
The custom timing command can be generated in any number of ways. For example, it can be automatic, or triggered by any number of events. Or an instruction can be received by one of the modules of FIG. 7, and be obeyed. In some embodiments, where operation 720 has taken place, the instruction can be generated and received responsive to parsing the identifying reply. In such instances, for example, it can be discerned from the identifying reply that the tag supports the custom timing command, and the instruction is thus generated. Then bits can be received, or looked up from a table stored in a memory, and so on. These bits can be prepared into one or more packets for transmission, and so forth.
In some embodiments, the tag is able to backscatter the second reply using the second reply timing regardless of what state it is in, at the time it receives the custom timing command of operation 770.
In other embodiments, the tag can have two states, namely an enabled state and a disabled state, as will be described in more detail later in this document. Briefly, if the tag is in the enabled state, it can operate as per the above. But if the tag is in the disabled state, if it were to receive the custom timing command, the second reply timing would not be different from the first reply timing, even if it backscattered the second reply.
In embodiments of the latter case, at an optional next operation 760, an Enable command can be caused to be transmitted while the tag is in the disabled state. In some instances, this would cause the tag to transition internally to the enabled state. In some instances, the Enable command can be the first command described above. In these cases, therefore, the second reply timing is different from the first reply timing responsive to receiving the custom timing command while the tag is in the enabled state.
An optional operation 780 can take place after operation 770. According to operation 780 a Disable command can be caused to be transmitted to the tag, while the tag is in the enabled state. This can cause the tag to transition internally to the disabled state.
FIG. 8 is a diagram illustrating commands that may be transmitted as a result of operations of the flowchart of FIG. 7 according to embodiments. A wave 812 is a special case of wave 112 of FIG. 1. An Enable command 860 is optionally sent first, according to operation 760. A custom timing command 870 is sent next, according to operation 770. Then a Disable command 880 is optionally sent, according to operation 780.
As will be realized, commands 860, 870, 880 can be configured in any number of ways. For example, if Enable command 860 is provided, it can be separate from custom timing command 870. Preferably, these are configured as separate standalone commands, each occurring at a single one of the communication sessions such as those of time interval 312 of FIG. 3. In addition, the tag need not backscatter a reply to any one of them individually.
In addition, command 870, plus optionally commands 860 and 880, may be used among other commands that will be transmitted to the tag in question, and possibly other tags. Equally, the optional first and second replies will be among other replies backscattered by the tag in question, and possibly other tags.
In some embodiments, a reader system component can perform a method according to flowchart 700 to communicate with a single tag. This can be accomplished if the tag is the only one in its field of view. Or, the tag in question can be within a population of tags, but it has been singulated. This means that the tag in question is the only one from the population that replies to the reader.
In other embodiments, a reader component can perform a method according to flowchart 700 to communicate with more than one tag. For example, custom timing command 870 can be transmitted to a population of tags, intending that they each backscatter a second reply using the second reply timing, either together, or at different times, or in response to subsequent commands.
In yet other embodiments, combinations are possible. For example, Enable command 860 might be sent to a population of tags before one of them is singulated. Then, custom timing command 870 might be sent to a tag that has been singulated, or to whole the population of tags.
Each one of commands 860, 870, 880 can be constructed in any number of ways. In some instances, they can be considered as custom commands as not being specified in a particular communication protocol. In some instances they would be standalone commands, made by a sequence of bits chosen so that they do not conflict with other commands of the protocol. In other instances, they can be commands with a custom payload. Such commands can be known to the protocol or not, and the payload can be used to distinguish among different custom commands, and optionally further transfer a parameter for the commands.
When commands are used that are known to the protocol, a section of their payload can be advantageously used for the purpose of implementing a custom command, such as commands 860, 870, 880. For example, it can be an enable payload, a disable payload, etc. Such a section in the payload can be a mask field, according to embodiments. For the Gen2 Spec, two such commands are the Select command and the BlockWrite command. Between these two candidate commands, it should be considered that the Select command can be transmitted before or after a tag is singulated out of its population, while the BlockWrite is better suited for singulated tags. In addition, the BlockWrite command is optional to the Gen2 Spec, and the tag would probably have to have a controller that can accept it.
Each one of commands 860, 870, 880 can thus be constructed as an implementation of this Select command or the BlockWrite command. In addition to responding to the payload implementing the custom command, the tag may further, or may not also respond to the underlying Select command or BlockWrite command. An example is now described in terms of the Select command, but would apply equally to the BlockWrite command.
FIG. 9A is a table illustrating the fields of the Select command of the Gen2 Spec. Version 1.1.0 of the Gen2 Spec is hereby incorporated by reference in its entirety. The fields of this Select command are explained in more detail in the above mentioned Gen2 Spec. In addition, the implementation of this Select command can have a custom payload so that it operates as Enable command 860, custom timing command 870, Disable command 880, and/or another custom command.
FIG. 9B is a table illustrating how a number of custom commands can be enabled in a reader and a tag. EBV stands for Extensible Bit Vector. The Mask Field can be partitioned as shown, into two primary subfields, named FEF and FCF.
The Feature Enabling Field (FEF) enables the tag to verify that it is a proper recipient for the command, by comparing the transmitted FEF value against a value in Membank. In this case, Membank can be EPC, TID or USER memory. As can be seen, the FEF can be further partitioned into subfields, for better clarity. Such subfields can include a Class Identifier, the MDID, and an Indicator Bit.
The Class Identifier can be two bits. For example, EPCglobal can correspond to a value of 10. This would allow the custom command to apply, for example, only to EPCglobal tags.
The MDID is the tag manufacturer's ID, which is stored in the tag's TID memory. For Impinj tags, this number is 000000000001 or 100000000001. The MDID allows a reader to select tags of only the manufacturer of interest. So, even if this Select command is transmitted and received before singulation, the Select command can select also according to the tag manufacturer's ID. This will cause the manufacturer's tags to be selected, and thus the reader can ensure prior knowledge of the tag manufacturer's identification.
The Indicator Bit can be set to 0 or 1. In the Gen2 spec, a tag model number follows the MDID. A bit of this model number can serve as the Indicator Bit, and can be interpreted as follows: If it is 0, the tags can interpret the command as an “ordinary” Select, and execute it per the Gen2 spec. Else, if it is 1, the tags can interpret the Select command as a custom instruction, and execute according to the FCF.
The Feature Command Field (FCF) can have a command code that indicates the number of the custom instruction. For example, a command code of 00000 could be the custom timing command. This permits 31 possible custom commands. In addition, a command code of 11111 could indicate an extended command code that extends into the subsequent data field.
The data field can contain data needed to implement the custom instruction, if any. Not all commands will use it. The data field can be variable in size. Its meaning will derive from the command codes.
In some embodiments, the tag may ignore the Target and Action field in the Select command, depending on whether these fields are relevant to the CI. In other embodiments, the tag may also set the appropriate flag.
In preferred embodiments, the entire Select command must be valid for the tag to accept and execute the custom command. That means valid values for Membank, Length, Pointer, Mask, CRC-16, etc. An example is now described.
FIG. 9C is a table showing sample values that can be used for the table of FIG. 9B. These could be used for a custom timing command. The Membank having a binary value of 10 point to the TID memory. The pointer having a hex value of 06h points to the last two bits of the class identifier. The length having a hex value of 14h points to a length of 20 bits that follow thereafter.
Everything described above in terms of readers and reader components finds some correspondence with tags and tag chips. In some instances, some of the above also describe features and behavior of tag chips.
FIG. 10 is a block diagram of an electrical circuit 1024 according to embodiments. Circuit 1024 may be formed in an IC of an RFID tag, such as IC 224 of FIG. 2. Circuit 1024 has a number of main components that are described in this document. Circuit 1024 may have a number of additional components from what is shown and described, or different components, depending on the exact implementation.
Circuit 1024 includes at least two antenna connections 1032, 1033, which are suitable for coupling to one or more antenna segments (not shown in FIG. 10). Antenna connections 1032, 1033 may be made in any suitable way, such as using pads and so on. In a number of embodiments more than two antenna connections are used, especially in embodiments where more antenna segments are used.
Circuit 1024 includes a section 1035. Section 1035 may be implemented as shown, for example as a group of nodes for proper routing of signals. In some embodiments, section 1035 may be implemented otherwise, for example to include a receive/transmit switch that can route a signal, and so on.
Circuit 1024 also includes a Power Management Unit (PMU) 1041. PMU 1041 may be implemented in any way known in the art, for harvesting raw RF power received via antenna connections 1032, 1033. In some embodiments, PMU 1041 includes at least one rectifier, and so on.
In operation, an RF wave received via antenna connections 1032, 1033 is received by PMU 1041, which in turn generates power for components of circuit 1024. This is true for either or both R→T and T→R sessions, whether or not the received RF wave is modulated.
Circuit 1024 additionally includes a demodulator 1042. Demodulator 1042 demodulates an RF signal received via antenna connections 1032, 1033. Demodulator 1042 may be implemented in any way known in the art, for example including an attenuator stage, an amplifier stage, and so on.
Circuit 1024 further includes a processing block 1044. Processing block 1044 receives the demodulated signal from demodulator 1042, and may perform operations. In addition, it may generate an output signal for transmission.
Processing block 1044 may be implemented in any way known in the art. For example, processing block 1044 may include a number of components, such as a processor, memory, a decoder, an encoder, and so on.
In a number of embodiments, processing block 1044 includes a state machine 1048. State machine 1048 retains the state of the tag, at least while circuit 1024 is powered. The state of the tag dictates which of the subsequently received commands the tag would respond to and how, and so on. State machine 1048 can be as is called for in the specified communications protocol, and adapted to further accommodate the custom timing command, with or without contradicting the operation of the protocol.
Circuit 1024 additionally includes a modulator 1046. Modulator 1046 modulates an output signal generated by processing block 1044. The modulated signal is transmitted by driving antenna connections 1032, 1033, and therefore driving the load presented by the coupled antenna segment or segments. Modulator 1046 may be implemented in any way known in the art, for example including a driver stage, amplifier stage, and so on.
In one embodiment, demodulator 1042 and modulator 1046 may be combined in a single transceiver circuit. In another embodiment, modulator 1046 may include a backscatter transmitter or an active transmitter. In yet other embodiments, demodulator 1042 and modulator 1046 are part of processing block 1044.
Circuit 1024 additionally includes a memory 1050, which stores data 1052. Memory 1050 is preferably implemented as a Nonvolatile Memory (NVM), which means that data 1052 is retained even when circuit 1024 does not have power, as is frequently the case for a passive RFID tag.
As already mentioned above, in some embodiments the custom timing command works only when the tag is in an enabled state, as opposed to a disabled state. An example is now described.
FIG. 11 is an optional partial state diagram 1148 of a state machine of a tag having an electrical circuit as shown in FIG. 10. State diagram 1148 can be implemented by state machine 1048. State diagram 1148 includes enabled state 1165, and disabled state 1185, which can be states as described above. In addition, an Enable command 1160 and a Disable command 1180 can be as described above. For example, the Enable command can cause the tag to transition to enabled state 1165. This can be either only from disabled state 1185, or by remaining there from enabled state 1165, and so on.
In some embodiments, enabled state 1165 and disabled state 1185 are provided in a way that does not define additional states in the underlying protocol. For example, for the Gen2 Spec, the initial Ready state can be a disabled state 1185, while one or more of the other states can be enabled states 1165. Or some of the other states can also be disabled state 1185.
In other embodiments, either one or both of enabled state 1165 and disabled state 1185 can be provided as states different from, and in addition to what is required by the Gen2 Spec. It should be remembered, however, that the invention may also be practiced with embodiments where the tag is always enabled to respond appropriately to the custom timing command by changing its reply timing, and has no disabled state.
Methods for RFID tags and tag chips are now described. These methods may be practiced by different embodiments, including but not limited to the tag embodiments described above. Such methods may be performed by a number of tags concurrently, or by a single tag, alone in a field of view or singulated from a population, as has already been described above. In addition, it will be recognized that such methods will be performed largely in response to reader methods, such as those of flowchart 700.
In some embodiments, a first command is received from an RFID reader. This would be the first command described above, as having been transmitted towards the tag.
Then a first reply is backscattered optionally by the tag responsive to receiving the first command. The first reply can be any reply specified by an applicable protocol for the first command. The first reply uses a first reply timing, which is typically a reply timing specified by the protocol, but can be any other reply timing.
FIG. 12 is flowchart 1200 illustrating sample methods for RFID tags according to embodiments. It will be recognized that a method according to flowchart 1200 will be performed largely in response to the method of flowchart 700 being performed.
According to optional operation 1210, a command to identify is received, which is the command caused to be transmitted at optional operation 710. In some embodiments, the command to identify can be considered to be the above-mentioned first command.
At optional operation 1220, an identifying reply is backscattered in response to the command, which is the reply received at operation 720. The identifying reply can be, for example, a random number, an Electronic Product Code (EPC), a TID, or other code stored in memory that identifies the tag or item it is attached to, or its capabilities to change its reply timing. In some embodiments, the identifying reply can be considered to be the above-mentioned first reply.
Operation 1270 of flowchart 1200 is now described. While the description of operation 1270 is somewhat out of turn for the flow of flowchart 1200, it is presented at this point in the document so that the description of the additional optional operations of flowchart 1200 taking place before operation 1270 will make sense.
At operation 1270, a custom timing command is received by the tag. The custom timing command is as described elsewhere in this document. Operation 1270 may be performed either at the same time as receiving the first command, or at a different time, e.g. by a different reader. For example, the first command may be received at a time that the tag is commissioned, while the custom timing command may be received months or years later. In such cases, the tag may have lost power after backscattering the first reply, and before receiving the custom timing command. In other instances, operation 1270 takes place during the same exchange as receiving the first command, without even losing power.
At a later operation 1275, the tag backscatters a second reply, which uses a second reply timing. The second reply timing is different from the first reply timing of the first reply, because the custom timing command has been received. This can be accomplished by the tag making appropriate internal adjustments, in operating its modulator. In addition, some of these adjustments may involve setting an internal flag, adjusting an internal state machine, and so on.
In some embodiments, the second reply is backscattered in response to receiving the custom timing command. In other embodiments, one or more intervening commands are received after the custom timing command, and the second reply is backscattered in response to receiving the one of these intervening commands.
In some embodiments, the reply timing is changed by the custom timing command only for the second reply, and the tag then reverts to using the first reply timing. In other embodiments, the reply timing is changed for more than one of the subsequent replies. For example, the tag could then receive a third command, and backscatter a third reply, with the third reply using a third reply timing different from the first reply timing. The third reply timing could be the same as or different than the second reply timing.
The effect of the custom timing command may or may not survive an interim loss of power, after the custom timing command is received. In some embodiments, the reply timing is changed permanently, while in others, if power is lost, the tag will reset to replying using the first reply timing.
As also mentioned above, in some embodiments, the tag is able to backscatter the second reply using the second reply timing regardless of what state it is in, at the time it receives the custom timing command according to operation 1270. In other optional embodiments, the tag can have two states, namely an enabled state and a disabled state, as described with reference to FIG. 11.
At optional operation 1260, the tag can receive an Enable command, such as the one transmitted at operation 760. At next operation 1265, the tag transitions internally to enabled state 1165. This can be done in preparation of operation 1270, when the custom command is received.
At optional operation 1280, the tag can receive a Disable command, such as the one transmitted at operation 780. At next operation 1285, the tag transitions internally back to disabled state 1185. This can be done after operation 1270, to cause the tag to revert to using the first reply timing in its further replies. The Disable command is not necessary to be implemented. For example, the tag could be automatically disabled after the second reply, or after a few replies, or upon reverting to another one of the specified states such as the Ready state of the Gen2 spec.
In addition, in the event that any of the received commands, such as the custom timing command, the Enable command, and the Disable command are implemented by the Select command of FIG. 9A, the tag can respond properly to it in addition to what is described with reference to the reply timings. For example, the tag can set or unset an internal selected flag, and so on. Plus, the tag may or may not issue a reply, since the Select command does not call for a reply. But it might, in a custom embodiment.
The reply timing can be changed in many different ways, as will be evident to a person skilled in the art in view of the present description. In many such embodiments, the reply timing is a delay, before the tag starts backscattering, after receiving its most recent command, namely the command it is responding to. This works at least in the Gen2 Spec, which calls for the vast majority of tag replies to be received within a specified time window after finishing transmitting a command. Accordingly, readers may have a time window during which to receive tag replies. Changing the delay may thus cause the tag reply to fall outside the window of readers that do not know better, as would be unauthorized readers. As such, practicing embodiments of the invention could increase privacy. Examples are now given.
FIG. 13 shows two timing diagrams 1310, 1330, for describing how the reply timing can change according to embodiments. Diagram 1310 shows a first command 1320, which finishes being transmitted at time T0. Diagram 1310 also shows a first reply 1325, backscattered in response to first command 1310, and which starts being transmitted at time T1. First command 1320 and first reply 1325 can be the first command and the first reply described above. Here the first delay is a between times T0 and T1. The first reply can include a functional content as called for the exchange by the protocol, for example a code stored in a memory, a random number, and so on. Such a functional content is implemented by replies whose bits are specified by the applicable protocol. For example, these replies for the Gen2 Spec are PC, EPC, RN16, etc.
Diagram 1330 shows an other command 1370, which finishes being transmitted at the same time T0, for comparison only with that of diagram 1310. Diagram 1330 also shows a second reply 1375, backscattered in response to other command 1370, and which starts being transmitted at time T2. The most recent command for second reply 1375 has thus been other command 1370, and thus second reply 1375 is has the second delay between times T0 and T2.
The reply timing has changed from diagram 1310 to diagram 1330, because the delay up to T2 is different than the delay up to T1, by an amount DT. It should be noted that, in this example, the delay up to T2 is longer than that up to T1, although that need not be the case. In fact, it could be the other way around. The changed reply timings can be used to enhance the privacy of using the tag, by making it harder to read by unauthorized readers.
Other command 1370 could be either the custom timing command, or a command that intervenes, being sent after the custom timing command. In fact, the custom timing command itself could call for no reply at all.
In addition, second reply 1375 encodes the same functional content as first reply 1325. In other words, second reply 1375 does the same function as first reply 1325, except that it is subject to a different delay. This can be accomplished in a number of ways. For example, second reply 1375 can be identical to first reply 1325, having the same bits. Or the bits can be substantially similar from what they would be, with only a few added or changed, for further preventing second reply 1375 from being read by unauthorized readers. Or the bits can be totally different, but still accomplish the same function.
FIG. 14 is a conceptual timing diagram for illustrating how an amount of delay DT in the reply timings of the embodiments of FIG. 13 can be further tuned according to embodiments.
A Tune command 1470 is caused to be transmitted by the reader, and received by the tag. Tune command 1470 can be any convenient command, such as the first command, the custom timing command, or other command in the communication. Tune command 1470 encodes a time-indicating parameter. The time indicating parameter can be encoded as data in the FCF subfield shown in FIG. 9B. The second reply timing is thus determined from the time-indicating parameter. In an embodiment of a reader component, the time-indicating parameter can be looked up from a desired value for the second reply timing.
In the example of FIG. 14, the time-indicating parameter is a two-bit field code 1472. Here it is shown with the possible values it can take. Each value results in a different delay DT, namely one of DT1, DT2, DT3, and DT4. These values for delay DT can optionally be used in embodiments of the invention such as those of FIG. 13. The delay DT can be expressed in number of clock cycles, in a number of RF cycles, or in other units of time convenient for this purpose. Thus, in one example, delay DT can have values chosen among 4 msec, 8 msec, 12 msec, and 16 msec. In addition, such a delay should not be too long, because then other communication may start taking place.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS7009495 *Oct 2, 2002Mar 7, 2006Battelle Memorial InstituteSystem and method to identify multiple RFID tagsUS7277016 *Sep 22, 2004Oct 2, 2007International Business Machines CorporationSystem and method for disabling RFID tagsUS7562083 *Nov 9, 2005Jul 14, 2009Alien Technology CorporationRFID Huffman encoded commandsUS7716160 *Nov 5, 2004May 11, 2010Alien Technology CorporationMethods and apparatuses to identify devicesUS7716208 *Nov 9, 2005May 11, 2010Alien Technology CorporationRFID handshakingUS20040046645Aug 7, 2003Mar 11, 2004Btg International LimitedEnhanced identification systemUS20040066281 *Oct 2, 2002Apr 8, 2004Hughes Michael A.System and method to identify multiple RFID tagsUS20050083178 *Oct 19, 2004Apr 21, 2005Atmel Germany GmbhMethod for selecting one or several transpondersUS20050231327 *Apr 13, 2005Oct 20, 2005Ulrich FriedrichMethod for selecting one or more transpondersUS20050242927 *Apr 27, 2005Nov 3, 2005Atmel Co.Communication method in RFID or remote sensor systemsUS20060044114 *Aug 25, 2005Mar 2, 2006Atmel Germany GmbhMethod for selecting one or more transpondersUS20060117066 *Nov 9, 2005Jun 1, 2006Smith John SRFID handshakingUS20060143163 *Nov 9, 2005Jun 29, 2006Smith John SRFID huffman encoded commandsUS20070069866 *Sep 29, 2006Mar 29, 2007Symbol Technologies, Inc.Truncation, compression, and encryption of RFID tag communicationsUS20070075838 *Oct 4, 2005Apr 5, 2007Symbol Technologies, Inc.Method and apparatus for avoiding radio frequency identification (RFID) tag response collisionsUS20070164851 *Jan 12, 2007Jul 19, 2007Cooper Scott ARfid reader q-parameter aided by rf power measurementUS20070285250 *Aug 8, 2007Dec 13, 2007Moskowitz Paul ASystem and Method for Disabling RFID TagsUS20080061941 *Jun 25, 2007Mar 13, 2008Martin FischerMethod, transponder, and system for secure data exchangeUS20080111661Nov 15, 2006May 15, 2008Symbol Technologies, Inc.Method and system for transmission power reduction in RFID interrogatorsUS20080180221 *Jan 30, 2007Jul 31, 2008Micron Technology, Inc.Systems and methods for RFID tag arbitration* Cited by examinerNon-Patent CitationsReference1EPCGlobal, Inc "Specification of RFID Air Interface-EPC Radio-Frequency Identity Protocols Class-1 Generation-2 UHF RFID Protocol for Communications at 860 MHz-960 MHz, Version 1.1.0." (a.k.a. "The Gen 2 Spec") EPCglobal Inc. Dec. 17, 2005, http://www.2Smart Card Alliance Identity Council. "Countless Smart Cards vs. EPC Gen 2 RFID Tags: Frequently Asked Questions." Smart Card Alliance (2006). Jul. 2006: 1-6.3Specification for RFID Air Interface: EPC(TM) Radio-Frequency Identity Protocols Class-1 Generation-2 UHF RFID Protocol for Communications at 860 MHz-960 MHz Version 1.1.0. 2004-2006 EPCglobal, Inc. Dec. 17, 2005: 1-100.4Specification for RFID Air Interface: EPC™ Radio-Frequency Identity Protocols Class-1 Generation-2 UHF RFID Protocol for Communications at 860 MHz-960 MHz Version 1.1.0. 2004-2006 EPCglobal, Inc. Dec. 17, 2005: 1-100.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8690057Apr 5, 2013Apr 8, 2014A-I Packaging Solutions, Inc.Radio frequency identification system for tracking and managing materials in a manufacturing processUS9224125Feb 26, 2014Dec 29, 2015A-1 Packaging Solutions, Inc.Radio frequency identification system for tracking and managing materials in a manufacturing processUS9489650Nov 24, 2015Nov 8, 2016A-1 Packaging Solutions, Inc.Radio frequency identification system for tracking and managing materials in a manufacturing processClassifications U.S. Classification340/572.1, 340/10.1, 340/10.2International ClassificationG08B13/14, H04Q5/22Cooperative ClassificationG06K7/0008, H04W84/18European ClassificationG06K7/00ELegal EventsDateCodeEventDescriptionFeb 25, 2008ASAssignmentOwner name: IMPINJ, INC., WASHINGTONFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ENYEDY, ARTHUR GUSTAV;DIORIO, CHRISTOPHER J.;KAVOUNAS, GREGORY T.;REEL/FRAME:020559/0662Effective date: 20080219Feb 28, 2012CCCertificate of correctionJun 2, 2015FPAYFee paymentYear of fee payment: 4RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services