Method and system of using active RFID tags to provide a reliable and secure RFID system

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 60/516,359 filed Oct. 31, 2003, the entirety of which is hereby incorporated by reference into this application.

[0002] 1. Field of the Invention

[0003] This invention relates generally to RFID (Radio Frequency Identification) systems and more specifically relates to a method and system of using active tags for providing a reliable and secure RFID system.

[0004] 2. Description of the Prior Art

[0005] RFID tags and readers have recently begun to enter the mass market. FIG. 1 illustrates a typical prior art RFID system, in which RFID reader 100 uses a first frequency to read RFID tags 117, 118, 119 and 120 in a large area that is populated with signposts 101–116. A second frequency is used to send commands from signpost 101–116 to the RFID tags 117, 118, 119 and 120. FIG. 2 shows a typical prior art RFID tag including low-frequency receiver 200, timer 201, microprocessor 202, UHF transmitter 203, and power source 204. Low-frequency receiver 200 receives commands from signposts 101–116 and UHF transmitter 203 sends data to RFID reader 100. A shortcoming of this prior art system is that the signposts cannot have overlapped zones and need careful cell planning, and the system needs at least two frequencies to operate and can encounter throughput problems when the RFID tag population increases in the large read zone of the RFID reader.

[0006] While this prior art system may be suitable to the early deployment of RFID applications, it is desirable to provide an improved system for reliability and throughput purposes in which a RFID reader network includes multiple readers using active RFID tags.

[0007] In view of the foregoing disadvantages inherent in the RFID system now present in the prior art, the present invention provides a method and system of using active tags for providing a reliable and secure RFID system. The method and system for providing a reliable and secure RFID system using active tags substantially departs from the concept and design of the prior art, and in so doing provides a reliable and secure reader network in which multiple RFID readers can simultaneously operate to provide a large area of coverage with minimal interference among the readers in the same network.

[0008] The present invention, which will be described subsequently in greater detail, provides a system to cover a large area using multiple readers that can simultaneously operate and a method to improve the system reliability. In this respect, before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in its application to the details of block diagrams and flow charts set forth in the following description of illustrated in the drawings. The invention is capable of other embodiments and being practiced and carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein are for the purpose of the description and should not be regarded as limiting.

[0009] The present invention generally comprises a RFID system including reliable RFID tags and a plurality of RFID readers that can simultaneously operate to improve the system throughput and reliability. The system of the present invention includes a large-zone RFID reader, a plurality of small-zone RFID readers, and a plurality of RFID tags. The large-zone RFID reader covers areas which are not covered by the small-zone RFID readers. The output power of the small-zone RFID readers is controlled by the large-zone RFID reader based on RFID tag operation patterns of the small-zone RFID readers. The system reliability is improved by a method that uses reliable RFID tags, RFID reader's beacon signals, and the RFID tag's repetitive transmitting signals to detect RFID tag failures. The system security is provided by a method that uses integrated crypto engines in both the RFID tags and RFID readers.

[0010] The present invention provides for a method of using multiple RFID readers that can simultaneously operate in different frequencies thereby providing enhanced system throughput.

[0011] The present invention also provides for a method of using multiple RFID readers that can simultaneously operate in a single frequency thereby providing enhanced system throughput.

[0012] The present invention also provides for a method of controlling the output power of small-zone RFID readers by a large-zone RFID reader to improve the overall system coverage and performance.

[0013] The present invention also provides for a method of using a change in associated RFID reader IDs of a moving RFID tag to set and clear its TRANSIT status.

[0014] The present invention also provides a system including a RFID tag using a separate transmitting and receiving antenna to improve system reliability.

[0015] The present invention also provides for a method of using RFID reader beacons and RFID tag's repetitive transmission signals to detect a RFID tag's transmitting or receiving failure.

[0016] The present invention also provides a system in which a RFID reader and RFID tag use integrated crypto engines to improve the system security.

[0017] To the accomplishment of the above, this invention may be embodied in the form illustrated in the accompanying drawings, attention being called to the fact, however, that the drawings are illustrative only, and that changes may be made in the specific construction illustrated.

[0046] Reference will now be made in greater detail to a preferred embodiment of the invention, an example of which is illustrated in the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings and the description to refer to the same or like parts.

[0047] FIG. 3 is a schematic diagram of RFID system 10 in accordance with the teaching of the present invention. RFID system 10 uses a large-zone RFID reader 300 and a plurality of small-zone RFID readers 301–316 cover a large area. A RFID tag and a RFID reader go through an association process, in which both the RFID tag and RFID reader send their identification (ID) numbers to each other and the RFID reader establishes a record that the RFID tag is currently connected to it. In the present invention, one or more active RFID tags 317–321 first try to become associated with small-zone RFID readers 301–316. The one or more active RFID tags 317–321 which cannot become associated with small-zone RFID readers 301–316 are associated with large-zone RFID reader 300. Accordingly, in the example shown in FIG. 3, active RFID tag 318 is associated with small-zone RFID reader 304. Active RFID tags 319 and 320 are associated with small-zone RFID reader 309. Active RFID tags 317 and 321 cannot be associated with any small-zone RFID reader 301–316 and are associated with large-zone RFID reader 300. Large-zone RFID reader 300 only handles active RFID tags 317 and 321 which are not covered by any small-zone RFID reader 301–316. Large-zone RFID reader 300 and small-zone RFID readers 301–316 can simultaneously operate using multiple frequencies providing improved overall system throughput and reliability. In a multiple-frequency environment, the frequencies Freq_S1–Freq_S5 of the RFID readers 300–316 are selected according to a frequency plan in which all the readers adjacent to each other use different frequencies. A user can locate an active RFID tag based on its association with a specific small-zone RFID reader 301–316.

[0048] FIG. 4 is a hardware block diagram of an embodiment of RFID tags 317–321 which comprise antenna 400, RF and baseband circuits 401, microprocessor 402, clock circuits 403, one or more memory devices 404, and crypto engine 405. Crypto engine 405 is a hardware circuit that performs calculation of encryption and decryption algorithms.

[0049] FIG. 5 is a typical hardware block diagram of an embodiment of small-zone and large-zone RFID readers 300–316, which comprise antenna 500, RF and baseband circuits 501, microprocessor 503, clock circuits 504, memory 505, crypto engine 506, and network interface 502.

[0050] FIG. 6 is a schematic diagram of a frame structure for the small-zone and large-zone readers, which includes an embodiment of beacon period 600, contention access period (CAP) 601, and scan period (SP) 602. A beacon frame structure comprises several fields including preamble 603, synchronization 604, RFID reader ID 605, beacon interval 606, CAP length 607, tag command 608, parameters 609, reserved field 610, and error control 611. Reserved field 610 is available for other uses. During a scan period, small-zone RFID readers 301–316 scan different frequency channels for RFID tag transmitting signals to make a association to one or more active RFID tags 317–321. After one or more active RFID tags are associated with a small-zone RFID reader, the active RFID tags stop sending signals to make a association and only communicate with the associated RFID reader during the contention access period (CAP) 601. Referring to FIG. 3, RFID tags 317–320 can move between different locations. After RFID tags 318–320 are associated with respective RFID readers 304 and 309, RFID tags 318–320 stop sending repetitive signals and only communicate with respective RFID readers 304 and 309.

[0051] FIG. 7 shows active RFID tag 703 which moves from location L1 to location L6 by going through different coverage areas of large-zone RFID reader 700 and small-zone RFID readers 701–702. Active RFID tag 703, large-zone RFID reader 700 and small-zone RFID readers 701–702 can have similar configurations as respective active RFID tags 317–321, large-zone RFID reader 300 and small-zone RFID readers 301–316, as described above.

[0052] FIG. 8 is a RFID tag state diagram for zone changes shown in FIG. 7. In STATE A, active RFID tag 703 cannot detect any reader beacon or reader acknowledgement (ACK). In STATE B, active RFID tag 703 is associated with SZR. In STATE C, active RFID tag 703 is associated with LZR. In STATE D, active RFID tag 703 loses its SZR reader beacon. At location L1 active RFID tag 703 remains in STATE A 800 when it cannot detect any beacon or ACK of a RFID reader. At location L2, active RFID tag 703 is scanned and becomes associated with large-zone RFID reader 700 and active RFID tag 703 goes to STATE C 802. At location L3, active RFID tag 703 enters STATE B 801 because it is associated with small-zone RFID reader 701. When active RFID tag 703 moves from location L3 to location L4, active RFID tag 703 first goes to STATE D 803 because of the loss of beacons from small-zone RFID reader 701 and then enters STATE B 801 after small-zone RFID reader 702 reads active RFID tag 703. There is a possibility that active RFID tag 703 loses RFID reader 701 beacons and is not detected by RFID reader 702 for a long period of time. In this case, active RFID tag 703 moves to STATE A 800 first and then STATE B 801. When active RFID tag 703 moves from location L4 to location L5, it first goes to STATE D 803 because of the loss of beacons from small-zone RFID reader 702 and then enters STATE C 802 after large-zone RFID reader 700 reads active RFID tag 703. Finally, active RFID tag 703 goes back to STATE A when active RFID tag 703 is outside the coverage areas of all of RFID readers 700–702.

[0053] FIG. 9 is a schematic diagram showing the signaling and communication operations for active RFID tag 703 in different states described in FIG. 7 and FIG. 8. In STATE A 800, active RFID tag 703 sends a repetitive signal for every T_A period because it cannot detect any RFID reader beacon or ACK. Typically T_A is selected to be the longest, repetitive time period for providing power-savings. In STATE B 801, active RFID tag 703 is associated with small-zone RFID reader 701 or 702. In STATE B 801, active RFID tag 703 stops sending any repetitive signals and communicates with RFID reader 701 or 702 only at the contention access period 601, shown in FIG. 6. In FIG. 9, in STATE C 802, active RFID tag 703 communicates with the large-zone RFID reader 700 in contention access period 601 and sends a repetitive signal for every time period T_C in scan period 602 to allow active RFID tag 703 to be read by small-zone RFID reader 701 or 702. In STATE D 803, active RFID tag 703 sends a repetitive signal for every time period T_D because active RFID tag 703 cannot detect the beacons sent by small-zone RFID reader 701 or 702 that were previously associated with active RFID tag 703.

[0054] FIG. 10 is a timing diagram for different RFID readers 301–306 operating in scan period 602. Active RFID tag 1000 sends out signaling packet 1001 to request association with any of small-zone RFID readers SZR1–SZR4 and large-zone RFID reader LZR. Although small-zone RFID reader SZR3 detects signaling packet 1001 and sends acknowledge (ACK) packet 1002, active RFID tag 1000 fails to receive ACK packet 1002 because it is too far away from RFID reader SZR3, and, hence, active RFID tag 1000 sends another signaling packet 1003. If small-zone RFID readers SZR1–SZR4 can all detect packet 1003, then each reader will listen to the channel for a monitoring window that is inversely proportional to received signal strength indicator (RSSI) before sending an ACK packet 1004. Typically, the monitoring widow of the large-zone reader (LZR) is greater than any monitoring window of the small-zone reader (SZR). In this example, small-zone RFID reader SZR1 has the strongest RSSI, so it has the shortest monitor window before sending ACK packet 1004. This approach improves the probability that the closest small-zone RFID reader SZR1 is the first one to send ACK packet 1002 or 1004. A typical request (REQ) packet 1001 or 1003 comprises several fields including preamble 1005, tag ID 1006, flag 1007, and error control 1008. A typical ACK packet 1002 or 1004 includes several fields, such as preamble 1009, reader ID 1010, RFID reader's channel number 1011, time for the next reader beacon 1012, and error control 1013. Active RFID tag 1000 uses reader's channel number 1011 and time of next beacon 1012 to go to small-zone RFID reader SZR1 beacon channel for completing the association process.

[0055] FIG. 11 is a flow chart for a RFID reader's scan task. The scan task starts from Step 1100 and selects a scan channel in Step 1101. The task listens to the scan channel in Step 1102 and checks if a valid tag request has been received in Step 1103. If there is a valid tag request, the task calculates the monitoring window based on received signal strength indicator (RSSI) in Step 1106. In step 1107, the task listens to the channel during a monitoring window. If there is another reader responding to the tag in Step 1108, the task then goes back to Step 1102 to listen to the channel again. Alternatively, if there is not another reader responding to the tag, the task sends an ACK packet to the tag in Step 1109. In Step 1103, if no valid tag request occurred, the task checks the channel timeout in Step 1104. If there is no timeout, the task goes back to Step 1102 to listen to the same channel. Alternatively, if there is a time out, the task goes to Step 1105 to check whether all the channels have been scanned. If all the channels have been scanned, the task stops in Step 1110. Alternatively, if all the channels have not been scanned, the task goes to Step 1101 to select a new channel to scan.

[0056] FIG. 12 is a schematic diagram of an active RFID tag and RFID reader operation in contention access period 601 in which the active RFID tags use a listen-before-talk approach to communicate with a RFID reader. After receiving a RFID reader beacon packet, each active RFID tag TAG1–TAG4 checks whether it needs to respond to the RFID reader based on the beacon's tag command 608 and parameter 609 fields, as shown in FIG. 6, or a tag-initiated event. If the RFID tag needs to respond, the active RFID tag waits for a randomly generated backoff window before sending a data packet to the RFID reader.

[0057] FIG. 13 is a flow chart of a RFID tag's communication task in contention access period 601. The task is initiated from Step 1300 when the RFID reader is trying to talk to the active RFID tag using the beacon's tag command 608 and parameter 609 fields or the active RFID tag has internal or external events needed to be reported to the RFID reader. The task waits for the beacon to end in Step 1301 and a backoff window in Step 1302. If the channel is clear in Step 1303, the task goes to Step 1305 and checks whether there is enough time to send a data packet before the end of contention access period 601. If there is not enough time to send a data packet, the tasks go back to Step 1301. If there is enough time to send a data packet, the task sends out the data packet in Step 1306. The task waits for a response packet from the RFID reader in Step 1307. In Step 1308, the task checks the validity of the RFID reader packet. If the RFID reader packed is valid, the task ends in Step 1309. If the RFID reader packed is not valid, the task goes to Step 1302. If the channel is not clear in Step 1303, the task waits for another active RFID tag to complete its operation in Step 1304 before going to Step 1302.

[0058] FIG. 14 is a flow chart for a RFID tag's transition task in State A 800. The task starts from Step 1400. The task sends out an association request in Step 1401. The task waits for an ACK packet from the reader or a timeout in Step 1402. If the task receives a small-zone RFID reader ACK packet in Step 1403, it sets a TRANSIT flag in Step 1410 and ends the task in Step 1411 at which the active RFID tag moves to State B 801. If the task receives a large-zone RFID reader ACK packet in Step 1404, it sets a TRANSIT flag in Step 1408 and ends the task in Step 1409 in which the task moves to State C 802. If no ACK packet is received in Step 1403 and Step 1404, the task checks whether the time that the task stays in State A 800 is greater than a predetermined threshold in Step 1405. If the time in State A is greater than a predetermined threshold, the task clears the TRANSIT flag in Step 1406. If the time in State A is not greater than a predetermined threshold, the task goes to Step 1407 to sleep for a T_A period before going back to Step 1401.

[0059] FIG. 15 is a flow chart for a RFID tag's transition task in State B 801. The task starts from Step 1500 and wakes up to listen to the RFID reader beacon in Step 1501. If the task receives a valid RFID reader beacon in Step 1502, it resets the count of loss of a beacon to zero in Step 1507. Alternatively, if the task does not receive a valid beacon from the RFID reader, the task increases the count of loss of a beacon by one in Step 1503. The task checks whether the count of beacon loss is greater than a threshold in Step 1504. If the count of a beacon loss is greater than a threshold, the task sets TRANSIT flag in Step 1505 and ends in Step 1506 where the RFID tag moves to State D 803. If the count of a beacon loss is not greater than a threshold, the task checks whether the time that it stays in State B 801 is greater than another threshold in Step 1508. If the time that it stays in State B 801 is greater than another threshold, the task clears the TRANSIT flag in Step 1509. If the time that it stays in State B 801 is not greater than another threshold, the task goes to Step 1510 to sleep for a beacon period before going back to Step 1501.

[0060] FIG. 16 is a flow chart for a RFID tag's transition task in State C 802. The task starts from Step 1600 and checks whether it is in the contention access period 601 of the large-zone RFID reader in Step 1601. If the task is not in the contention access period 601 of the large-zone RFID reader 300, the task sends out an association request in Step 1602 and waits for an ACK packet from the small-zone RFID reader 301–316 or a timeout in Step 1603. If the task receives a small-zone RFID reader ACK packet in Step 1604, the task sets a TRANSIT flag in Step 1611 and ends the task in Step 1612 in which the RFID tag moves to State B 801. If the task does not receive a small-zone RFID reader ACK packet, the task checks whether it loses the association with the large-zone RFID reader in Step 1605. If the task loses the association with the large-zone RFID reader, the task sets the TRANSIT flag in Step 1606 and ends in Step 1607 in which the tag moves to State A 800. If the task does not lose the association with the large-zone RFID reader, the task checks whether the time that it stays in State C 802 is greater than a threshold in Step 1608. If the time that it stays in State C 802 is greater than a threshold, the task clears the TRANSIT flag in Step 1609. If the time that it stays in State C 802 is not greater than a threshold, the task goes to Step 1610 to sleep for a T_C period before going back to Step 1601.

[0061] FIG. 17 is a flow chart for an active RFID tag's transition task in State D 803. The task starts from Step 1700 and sends out an association request in Step 1701. The task waits for an ACK packet from the RFID reader or a timeout in Step 1702. If the task receives a small-zone RFID reader ACK packet in Step 1703, it sets a TRANSIT flag in Step 1709 and ends the task in Step 1710 in which the RFID tag moves to State B 801. If the task receives a large-zone RFID reader ACK packet in Step 1704, it sets a TRANSIT flag in Step 1705 and ends the task in Step 1706 in which the task moves to State C 802. If no ACK packet is received in Step 1703 and Step 1704, the task checks whether the time that it stays in State D 803 is greater than a predetermined threshold in Step 1707. If the time that it stays in State D 803 is greater than a predetermined threshold, the task clears the TRANSIT flag in Step 1711 and ends the task in Step 1712 where the RFID tag moves to State A 800. If the time that it stays in State D 803 is not greater than a predetermined threshold, the task goes to Step 1708 to sleep for a T_D period before going back to Step 1701.

[0062] FIG. 18 is an embodiment of RFID system 1830 using a single frequency in which large-zone RFID reader 1800 and a plurality of small-zone RFID readers 1801–1816 are used to cover a large area. Active RFID tags 1817–1821 first try to be associated with small-zone RFID readers 1801–1816 so that large-zone RFID reader 1800 only handles tags 1817, 1821 that are not covered by any small-zone RFID reader 1801–1816. All of large-zone RFID reader 1800 and small-zone RFID readers 1801–1816 can simultaneously operate using a single frequency by using a time-division approach. A user can locate an active RFID tag based on its association with a specific small-zone RFID reader 1801–1816.

[0063] FIG. 19 is a schematic diagram of operations of a plurality of RFID readers using a single frequency. As described in FIG. 6, the frame structure of either a large-zone RFID reader or a small-zone RFID reader comprises beacon 600, contention access period 601, and scan period 602. In a single frequency operation, small-zone RFID readers 1801–1816 use the large-zone RFID reader 1800 beacon as a reference to offset their beacon timing by contention access period 601 plus a small random time period, so that the RFID tags can communicate with their associated RFID readers with minimal interference from other RFID tags and RFID readers. For example, the small random time period can be in the range of about 0 microsecond to about 100 microseconds. In this embodiment, the scan period (SP) of the large-zone reader (LZR) is between the end of a first contention access period (CAP) of large-zone RFID reader 1800 and beginning of a second beacon period of large-zone reader (LZR). The scan period of a first small-zone reader (SZR1) is between the end of a first contention access period (CAP) of small-zone reader (SZR1) and beginning of a second beacon period of small zone reader (SZR1).

[0064] FIG. 20 is a flow chart for a beacon task of a small-zone RFID reader in a single-frequency environment. The task starts from Step 2000 and goes to Step 2001 where the task listens to the channel. The task locates the large-zone RFID reader's beacons and waits until the large-zone RFID reader completes its contention access period (CAP) 601. The task listens to the channel for an additional random period in Step 2002 before checking whether there are beacon signals from other small-zone RFID readers in Step 2003. If there are beacon signals from other small-zone RFID readers, the task waits for the end of the CAP of the small-zone RFID reader in Step 2004 and then goes to Step 2002. If there are no beacon signals from other small-zone RFID readers, the task sets the timer for generating its beacon and sends out the beacon packet in Step 2005 and ends in Step 2006.

[0065] FIGS. 21A–21C are schematic diagrams showing three different coverage areas for small-zone RFID readers. In an embodiment shown in FIG. 21A, there are large overlapped areas among all the small-zone RFID readers. In this embodiment, most of the active RFID tags are associated with the small-zone RFID readers, and the large-zone RFID reader has little traffic and few associated active RFID tags. In an embodiment shown in FIG. 21B, there are large disjointed areas among all of the small-zone RFID readers. In this embodiment, the large-zone RFID reader handles a large number of active RFID tags. This embodiment can cause throughput and reliability issues. FIG. 21C illustrates control of the small-zone RFID readers by the large-zone RFID readers. The original coverage is shown in FIG. 21B. FIG. 21C illustrates that the large-zone RFID reader requests each of the small-zone RFID readers to increase its radio output power and hence its coverage area until the large-zone RFID reader's traffic and tag association falls below a predetermined high threshold. If the original coverage is shown in FIG. 21A, FIG. 21C illustrates that the large-zone RFID reader requests each of the small-zone RFID readers to reduce its radio output power and hence its coverage area until the large-zone RFID reader's traffic and tag association exceeds a predetermined low threshold.

[0066] FIG. 22 is a flow chart for a power control task of a large-zone RFID reader. The task starts from Step 2200 and gets N_T, the number of tags associated with the large-zone RFID reader at time T, in Step 2201. If the N_T is greater than a maximum threshold in Step 2202, the task goes to Step 2207 to check whether N_T is less than N_T−1. If N_T is not less than N_T−1, the task increases the step number for increment (SNI) by one in Step 2209. If N_T is less than N_T−1, the task sets the SNI to zero in Step 2208. The task checks whether SNI is greater than a threshold in Step 2210. If SNI is not greater than a threshold, the task sends request to the small-zone RFID readers for increasing their output power. If SNI is greater than a threshold, the tasks goes to Step 2204 where the task waits for a time period for the system to settle into the new adjustment in Step 2204. If the N_T is less than a minimum threshold in Step 2203, the task goes to Step 2212 to check whether N_T is greater than N_T−1. If N_T is not greater than N_T−1, the task increases the step number for decrement (SND) by one in Step 2214. If N_T is greater than N_T−1, the task sets the SND to zero in Step 2213. The task checks whether SND is greater than a threshold in Step 2215. If SND is not greater than a threshold, the task sends a request to the small-zone RFID readers for decreasing their output power. If SND is greater than a threshold the task goes to Step 2204. In Step 2205, the task checks whether there is an event to stop power control task. If there is an event to stop power control task, the task ends in Step 2206. If there is not an event to stop power control task, the task goes to Step 2201.

[0067] FIG. 23 is a schematic diagram of transmitting and receiving faults of an active RFID tag. In the normal condition 2300, the active RFID tag 2303 has a two-way communication with the RFID reader 2304. If there is a fault in the RFID tag's transmission path 2301, including hardware failure or a blocked transmitting path, active RFID tag 2303 can only receive RFID repetitive beacons from RFID reader 2304. If there is a fault in the tag's receiving path 2302, including hardware failure or a blocked receiving path, RFID reader can only receive repetitive request signals from active RFID tag 2303. A description of detection of a RFID tag transmitting fault is listed in Table 1.

[0068]

TABLE 1
Detection of the tag's transmitting fault
State	Transmitting Fault Detection
A 800	Tag randomly wakes up to listen and starts a timer when it
	detects a reader beacon. The fault indicator is triggered when the
	timer exceeds a threshold and the reader is still not responding to
	the tag.
B 801	Tag starts to count number of times that its transmitted packets
	are not acknowledged by the small-zone RFID reader. The fault
	indicator is triggered when the number exceeds a threshold.
C 802	Tag starts to count number of times that its transmitted packets
	are not acknowledged by the large-zone RFID reader. The fault
	indicator is triggered when the number exceeds a threshold.
D 803	There is no need for fault detection in State D because of its
	short duration.

[0069] The tag's receiving fault 2302 is detected by the RFID reader that starts to count the number of times that it sends the packets to respond to the tag's association or data packets without tag's acknowledgement. The tag failure event is triggered when the number exceeds a threshold, and the event is sent to an external device, such as a backend server or RFID controller, linked to the RFID reader.

[0070] FIG. 24 is a hardware block diagram of a reliable RFID tag device including transmitting antenna 2400, receiving antenna 2401, transmitter/receiver/baseband circuits 2402, microprocessor 2403, clock circuits 2404, memory 2405, and transmitting failure indicator 2406. The use of separate transmitting antennas 2400 and receiving antennas 2401 improves RFID tag reliability. The system can detect failures as long as either one of the transmitting or receiving paths works. The transmitting fault indicator can be a light or sound generating device. In the event that the active RFID tag's transmitting path fails, transmitting fault indicator 2406 provides a means to inform the outside world about the transmitting failure 2302.

[0071] FIG. 25 is a sequence diagram for security operations between an active RFID tag and RFID reader. When the RFID reader sends a read or write command, the active RFID tag responds with a challenge for tag authority. The RFID reader then sends response within the session key to the active RFID tag. The response with the session key is used by both the active RFID reader and RFID tag to encrypt data for communication between them.

[0072] FIG. 26 is a flow chart for an active RFID tag's read/write task. The task starts from Step 2600 and generates a challenge to the RFID reader in Step 2601. The task waits for the RFID reader's response or a timeout event in Step 2602. If the response is not valid in Step 2603, the task ends in Step 2606. If the response is valid, the task extracts the session key from the reader's response in Step 2604 and completes the read or write operation by using the session key to decrypt or encrypt data in Step 2605.

[0073] FIG. 27 is a flow chart for a RFID reader's read/write task. The task starts from Step 2700 and sends a read or write request to the RFID tag in Step 2701. The task waits for the tag challenge or a timeout event in Step 2702. The task checks whether the challenge is valid in Step 2703. If the challenge is not valid, the task ends in Step 2706. If the challenge is valid, the task generates and sends a response with the session key to the RFID tag in Step 2704 and completes the read or write operation by using the session key to decrypt or encrypt data in Step 2705.

[0074] It is to be understood that the above-described embodiments are illustrative of only a few of the many possible specific embodiments, which can represent applications of the principles of the invention. Numerous and varied other arrangements can be readily devised in accordance with these principles by those skilled in the art without departing from the spirit and scope of the invention.