RFID, NFC & UWB · Study deck

RFID Design and Deployment

Picture a tagged medicine tray moving through a doorway.

Radio Remi is your guide for this deck.

deployment

Radio Remi, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

Choose LF, HF/NFC, UHF, semi-passive, or active RFID from workflow constraints rather than range claims alone.
Plan a site survey that separates intended read zones, no-read zones, materials, tag orientation, reader power, and antenna placement.
Use a first-pass link budget to explain why practical read distance differs from ideal free-space behavior.
Tune dense-tag portal designs with dwell time, antenna geometry, and EPC Gen2 Q-algorithm settings.

Major section

Start With the Story

A bench reader sees it every time, but metal carts and liquid packs change the path and may create misses or reads from the next lane.

Near field communication, or NFC, is a short-range radio method for nearby exchanges.
Radio frequency means the rate of a radio wave.
Radio frequency identification, or RFID, uses radio to identify a tag.
The right family depends on range, material, motion, and workflow.

Major section

Design Boundary

A deployment plan should make every approval dependency visible before hardware is ordered.

Requirements state the item and place; frequency fit narrows the radio choice, while tag and antenna placement define the intended field.
A site survey tests that field before a pilot records missed, duplicate, and cross reads.
Rollout is justified only while that linked evidence remains current.

RFID deployment review moves from requirements and frequency fit through physical tag and antenna planning, pilot read evidence, event filtering and audit contract, then a rollout gate with retest triggers.

Major section

Design Boundary (continued)

Middleware then turns raw observations into a named event contract, which the rollout gate can approve or send back for retest.

Packaging, antenna layout, reader settings, or event rules can change the result.
Preserve the requirement, setup, pilot trace, and event rule together so a changed design cannot inherit an old pass.
Middleware converts those observations into a named event contract before rollout is approved.

Major section

Deployment Is RF Engineering, Not Just Mounting · Frequency and Tag Fit

A UHF RFID install succeeds or fails on three coupled choices: the antenna polarization, the shape of the read zone, and the event rule that decides when raw reads become an accepted workflow event.

The dwell time is therefore 2.4 m / 1.2 m/s = 2.0 s.

RFID read-zone evidence loop connecting requirements, antenna geometry, inventory behavior, middleware filtering, and measured evidence.

Major section

Site Survey and Read-Zone Planning

The zone-width and item-speed relation gives a dwell-time estimate, but the actual passage test must measure target reads and stray observations.

A high target-read count is not enough if the portal also claims items that never crossed.
Reader antennas are mounted on the doorway frame, with cables routed toward nearby equipment.

RFID portal planning diagram showing two directional antennas, intended read zone, no-read zones, tag movement, dwell time, reader settings, and middleware evidence.

Major section

Site Survey and Read-Zone Planning (continued)

The survey checklist below captures each of those dependencies so the installed test can be repeated.

After reviewing the planned geometry, inspect Figure: An RFID portal surrounds a pallet of stacked to see the physical constraints that the survey must record rather than assume.
The installed portal in Figure: An RFID portal surrounds a pallet of stacked shows the geometry that a read-zone test must record.
Antenna height, angle, beam direction, mounting, and cable condition can all change which moving tags are observed.
The photograph gives a real installation form but no measured read rate or exclusion result.

An RFID portal surrounds a pallet of stacked black containers between two tall reader columns, with overhead bars linking the columns. The image shows the installed passage but no measured antenna angle or read-zone record.

Major section

Link Budget and Practical Read Distance

A link budget is a screening tool.

It explains why a design might work, but it does not replace an installed pilot.
For passive UHF systems, also remember that the reader must hear the tag backscatter.
A forward-link estimate can look acceptable while the return path or anti-collision timing still fails in production.

Major section

Polarization, Link Margin, And Zone Shape

The first design pass should put numbers beside the physical choices.

Linear polarization can deliver stronger coupling when the tag orientation is known; circular polarization usually gives up some peak coupling to tolerate random tag angles.
The right choice depends on how the object actually moves through the read zone.
The second screen is dwell time.

Major section

Polarization, Link Margin, And Zone Shape (continued)

At 915 MHz, wavelength is about 0.328 m.

At 3 m, free-space path loss is 20 log10(4 pi d / lambda), or about 41.2 dB.
If the chosen tag threshold is -18 dBm, this example has about 6.8 dB of forward-link margin before real-site variation.
If the log shows all expected tags quickly but the application creates repeated arrivals, the fix is deduplication and idempotency.

Major section

Dense-Tag Portals and Anti-Collision · Dense-Reader Planning

Warehouse, laboratory, and retail portals fail when the read zone is physically correct but the tags do not remain in the field long enough to complete inventory rounds.

When several readers run near each other, the core problem is a power mismatch: a reader transmits watts of carrier, while a tag answers with a faint backscattered reflection.
One reader's transmission can drown a neighbor's tag replies, which is reader-to-reader interference.
Dense portals also have a tag-population problem.

Major section

Deployment Failure Patterns · Pilot Acceptance Record

Assuming every pass will be complete: RFID reads are probabilistic in real environments.

Selecting frequency by distance alone: UHF can be the right choice for bulk inventory, but metal, liquid, orientation, and neighboring lanes can dominate the design.
HF or LF may be better when proximity and material tolerance matter more than bulk speed.
Treating middleware as a pass-through: Readers can report repeated observations, stale observations, and cross reads.

Deck summary

Key takeaways

A bench reader sees it every time, but metal carts and liquid packs change the path and may create misses or reads from the next lane.

A deployment plan should make every approval dependency visible before hardware is ordered.
Middleware then turns raw observations into a named event contract, which the rollout gate can approve or send back for retest.
A UHF RFID install succeeds or fails on three coupled choices: the antenna polarization, the shape of the read zone, and the event rule that decides when raw reads become an accepted workflow event.
A link budget is a screening tool.

Retrieval practice

Recall check 1 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q1In RFID deployment, what should decide the frequency family, and how is the choice confirmed?

AWhichever frequency the first available reader happens to support

BChoose UHF for rapid inventory, then confirm the reader's bench throughput.

CUse case and read-zone requirements, proven in an installed pilot

DWhatever band the tag vendor stocks in the largest quantity

Show answer

Answer: C Frequency family follows the use case and read-zone needs, validated by an installed-site pilot rather than a bench demo.

Retrieval practice

Recall check 2 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q2A forward-link estimate looks good, but wrapped products are missed at the dock. What does that show?

AUse forward-link range as proof of dock reads

BRead zone needs loss and tag-reply tests.

COnly the warehouse database is at fault

DIncrease range until neighboring lanes read too

Show answer

Answer: B A screening estimate cannot guarantee the real forward and return paths.

Retrieval practice

Recall check 3 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q3A dense portal uses an inventory setting far above its tag population. What should the team inspect?

AInspect the middleware event name for slot waste.

BInspect the reader's advertised range for slot waste.

CInspect empty slots and dwell-window reads for oversizing.

DInspect tag case colour for slot waste.

Show answer

Answer: C Excess slots can waste the time tags spend in the portal.

Retrieval practice

Recall check 4 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q4A team validates UHF tags on loose sample items in a clean test room, then installs the same tags on products stored against metal shelving. The production read rate drops sharply. What is the best first engineering response?

AIncrease every reader to maximum transmit power and then continue the rollout as planned.

BAssume the reader firmware is defective because the clean-room test had passed.

CReplace the deployment with barcodes without first measuring the failed read zones.

DRun an installed-site pilot for placement, orientation, materials, and no-read zones.

Show answer

Answer: D Metal shelving detunes and blocks UHF, so the first step is an installed-site pilot covering tag placement, orientation, shelf material, antenna angles, and no-read zones.

Retrieval practice

Recall check 5 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q5Eight dock-door readers are installed side by side. Individually each reads well, but with all of them enabled read rates collapse. What is the mechanism and the correct fix?

AReader carriers swamp backscatter, so schedule their frequency and time.

BWeak tag power limits the reads; increase transmit power at the dock doors.

CThe readers overheat when run together, so simply space them further apart.

DFit linear antennas to improve coupling to tags aligned along the dock-door path.

Show answer

Answer: A Reader-to-reader interference is the carrier-versus-backscatter power gap; dense-reader mode plus frequency hopping, listen-before-talk behavior, or other frequency/time planning coordinates nearby readers.

Print reference

Answers 1 of 2

Answer key.

C · Frequency family follows the use case and read-zone needs, validated by an installed-site pilot rather than a bench demo.
B · A screening estimate cannot guarantee the real forward and return paths.
C · Excess slots can waste the time tags spend in the portal.
D · Metal shelving detunes and blocks UHF, so the first step is an installed-site pilot covering tag placement, orientation, shelf material, antenna angles, and no-read zones.

Print reference

Answers 2 of 2

Answer key.

A · Reader-to-reader interference is the carrier-versus-backscatter power gap; dense-reader mode plus frequency hopping, listen-before-talk behavior, or other frequency/time planning coordinates nearby readers.