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.
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.
- The remaining question is antenna layout, or event rules change.
- The conclusion in design boundary now has a named boundary.
- Middleware converts those observations into a named event contract before rollout is approved.
- Rollout is justified only while that linked evidence remains current.
Major section
Deployment Is RF Engineering, Not Just Mounting
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.
Major section
Deployment Is RF Engineering, Not Just Mounting (continued)
None of these are visible in a data sheet's "read range" number, which is measured under controlled conditions with a tag orientation and environment that may not match the site.
- The tagged pallet is about 1.2 m long, the intended read zone is 2.4 m deep, and the forklift crosses at 1.2 m/s.
- The hand-off to filter to events needs an assigned owner.
- Reopen deployment is rf engineering, not just mounting whenever geometry and power changes.
Major section
Frequency and Tag Fit
Frequency selection is a fit decision, not a ranking.
- The useful question is: "Which field behavior supports this workflow with the fewest unresolved assumptions?".
- Identification is close and deliberate.
- The installation must tolerate tissue, water, dirt, or rugged mounting better than it needs high throughput.
- The workflow can accept short read distance and lower data rate.
Major section
Frequency and Tag Fit (continued)
A deliberate tap or close pass is desirable.
- The system needs compatibility with NFC-capable phones or established HF card/tag workflows.
- The workflow needs bulk reads, dock-door portals, handheld inventory, or item-level scanning across a larger read zone.
- The environment can be engineered for tag orientation, packaging, spacing, and antenna placement.
Major section
Frequency and Tag Fit (continued)
The design can tolerate RF sensitivity to metal, liquid, multipath, and neighboring read zones.
- The tag must run a sensor or keep local state but still depends on a reader interaction for the workflow.
- Battery service is acceptable and is part of the maintenance plan.
- The workflow needs beaconing, coarse location, or wider-area tracking that passive tags cannot support.
- Battery life, replacement process, device identity, and monitoring are managed as operational requirements.
Major section
Site Survey and Read-Zone Planning
The survey checklist below captures each of those dependencies so the installed test can be repeated.
- After reviewing the planned geometry, inspect Figure: An installed RFID portal whose antenna height to see the physical constraints that the survey must record rather than assume.
- Placement around overhead frame still needs testing.
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-Reader Planning
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.
- If a pallet has 48 case tags, the starting Q value should be near ceil(log2(48)) = 6, giving 2^6 = 64 slots.
Major section
Dense-Reader Planning (continued)
Starting at Q=4 gives only 16 slots, or 48 / 16 = 3 tags per slot on average, so the log should show many collisions.
- In the US UHF band, readers frequency-hop across permitted channels; in European deployments, fewer UHF channels and listen-before-talk behavior are part of channel access planning.
- The operational lesson is the same without relying on one regulatory clause number: dense deployments are planned in frequency and time, not only in space.
- Antenna spacing helps, but it is incomplete unless reader profiles, channel behavior, transmit timing, and no-read zones are validated together.
Major section
Deployment Failure Patterns
The approved placement should be part of the deployment specification.
- 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.
- Tune power with antenna direction, shielding, and no-read tests.
Major section
Deployment Failure Patterns (continued)
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.
- Middleware must deduplicate, reject, timestamp, map, and audit events without hiding the raw evidence needed for debugging.
- Leaving tag placement flexible: A tag moved a few centimeters can change coupling, polarization, and shielding.
- Maximizing reader power by default: More power can enlarge unwanted read zones.
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.
- 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.
- None of these are visible in a data sheet's "read range" number, which is measured under controlled conditions with a tag orientation and environment that may not match the site.
Retrieval practice
Recall check 1 of 3
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?
Show answer
Answer: A 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 3
Radio Remi says: answer from memory, then check your reasoning.
Q2A 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?
Show answer
Answer: B 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 3 of 3
Radio Remi says: answer from memory, then check your reasoning.
Q3Eight 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?
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
Answer key.
- A · Frequency family follows the use case and read-zone needs, validated by an installed-site pilot rather than a bench demo.
- B · 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.
- 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.