09.03.2013 Views

BLOCKING READER: DESIGN AND IMPLEMENTATION OF A ...

BLOCKING READER: DESIGN AND IMPLEMENTATION OF A ...

BLOCKING READER: DESIGN AND IMPLEMENTATION OF A ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

analysis. But all this Reader systems contain all this basic functional blocks shown<br />

in the Figure 5.1.<br />

5.2 Low-Cost Reader Requirements<br />

Research is still going to come up with a low cost RFID systems so that it can<br />

be extensively used in many applications. The RFID Reader Tag technology replaces<br />

the barcode technology. Barcodes and the barcode readers costs a lot less compared<br />

to a RFID tag and reader. Currently a RFID passive tag is greater than 8 cents and a<br />

typical low cost Reader is about $200-$500. But a barcode reader is as low as $18. So<br />

it is important to have a Ultra low-cost Reader and Tag. A lot of research is going on<br />

on designing a low cost UHF passive tags. The Auto-ID Center is developing low-cost<br />

radio frequency identification (RFID) based systems with the initial application as<br />

next generation bar-codes[45]. Based on the assumptions on the deployment of RFID<br />

technology the estimated cost of a passive tag in 10 years would be $0.02 [32]. So a<br />

0.01cent tag and 10 dollar reader can change the use of RFID systems. And we could<br />

see its deployment in many fields and applications.<br />

5.3 Possible Low-Cost Reader Architectures<br />

The design presented in this paper has the following design constraints<br />

• The cost the Reader design should be as low as 30$.<br />

• The Reader should comply on Gen 2 protocol.<br />

• Reader functionality should support read/write information to tags.<br />

• Radiated power should not exceed 1W.<br />

• Achievable read of 100 tags/sec.<br />

44

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!