Showing posts with label RFID. Show all posts
Showing posts with label RFID. Show all posts

Sunday, 25 October 2026

Bluetooth, BLE, UWB, RFID, and nRF(NFC): What Is the Same, What Is Different

Standard

 

Five names show up on every short-range wireless slide. Four of them are radios or tag systems. One of them is a chip brand. Teams mix them up, then pick the wrong one and spend a year fixing range, battery, or cost.

This post puts Bluetooth Classic, Bluetooth Low Energy (BLE), Ultra-Wideband (UWB), Radio-Frequency Identification (RFID), and Nordic nRF next to each other: what they share, where they split, and which use case each one actually wins.

Key Abbreviations in This Post

  • BT (Bluetooth Classic): The original Bluetooth radio. Built for audio and continuous data, not tiny coin-cell sensors.
  • BLE (Bluetooth Low Energy): A different Bluetooth radio mode. Same 2.4 GHz band, much lower power, used for sensors, beacons, and phone pairing.
  • UWB (Ultra-Wideband): Short pulses over a very wide band. Measures time of flight to get distance to about 10 cm.
  • RFID (Radio-Frequency Identification): A reader talks to a tag. Many tags are passive: no battery. Used to identify things, not to stream music.
  • NFC (Near-Field Communication): A short-range HF RFID flavor (13.56 MHz). Payments and tap-to-pair. About 4 cm.
  • nRF: Nordic Semiconductor's chip family (nRF52, nRF53, nRF54). Hardware that usually runs BLE, Thread, or Matter. Not a radio standard.
  • RSSI (Received Signal Strength Indicator): How loud the radio sounds. Used to guess distance. Often wrong by meters.
  • ToF (Time of Flight): How long the radio wave takes to travel. Used by UWB for real distance.
  • SoC (System on Chip): Processor, radio, and memory on one die. An nRF52840 is an SoC.

The One-Minute Version

  • Same job, different physics: all five show up in "talk to a nearby thing" products. They do not do that job the same way.
  • Bluetooth Classic: headphones, speakers, car audio. Needs more power. Streams data.
  • BLE: sensors, beacons, phone apps, "find my" wake-up. Cheap, everywhere, bad at exact distance.
  • UWB: "how far, and in which direction, for real." Car keys, AirTag arrows, warehouse safety.
  • RFID: "what is this tag?" Access cards, inventory, livestock. Passive tags can last forever.
  • nRF: the silicon you solder when the product speaks BLE (and often Thread or NFC). You still choose the protocol.

One Picture of the Family

Protocols vs a chip Four ways to talk. One piece of silicon that often runs BLE. Bluetooth Classic / BR-EDR 2.4 GHz Audio + data Headphones, cars Protocol BLE Low energy mode 2.4 GHz Sensors, beacons Phones everywhere Protocol UWB Time of flight 3.1 to 10.6 GHz ~10 cm distance Keys, finders Protocol RFID Reader + tag LF / HF / UHF ID, not a stream Cards, pallets Protocol family nRF = Nordic chip (SoC), not a fifth radio Typical firmware: BLE, Thread, Zigbee, Matter. Some parts add NFC. You buy nRF to implement BLE. You do not "install nRF" the way you enable UWB.

If you remember one line: Bluetooth, BLE, UWB, and RFID are how devices talk. nRF is a part you buy so a device can talk BLE.

What Is the Same

They overlap because products need the same three verbs: find, identify, connect.

  • Short range. Meters to tens of meters for most jobs. Not a cellular replacement.
  • Unlicensed or shared bands for the radio flavors (2.4 GHz for BT/BLE; 3.1 to 10.6 GHz for UWB; several RFID bands).
  • A reader and a thing. Phone and earbuds. Phone and tag. Gate and badge. Forklift and badge.
  • Often stacked. An AirTag uses BLE to be discovered and UWB to draw the arrow. A hotel lock may use RFID for the card and BLE for the phone.
  • Security is optional until it is not. Pairing, encryption, and distance-bounding are add-ons. Cheap beacons and cheap RFID tags are easy to clone if you skip them.
The shared loop 1. Find Nearby? In range? → 2. Identify Which tag or device? → 3. Act Unlock, play, count, stop RFID is strong at Identify. BLE is strong at Find + cheap data. UWB is strong at Find with proof of distance. Bluetooth Classic is strong at Act when Act means audio or a fat data pipe.

What Is Different

Bluetooth Classic BLE UWB RFID nRF
What it is Radio protocol Radio protocol Radio protocol Tag + reader family Chip / SoC brand
Main job Stream audio / data Low-power connect Measure distance Identify a tag Run the firmware
Band 2.4 GHz 2.4 GHz 3.1 to 10.6 GHz 125 kHz, 13.56 MHz, 860 to 960 MHz Depends on radio on the die (usually 2.4 GHz)
Typical range 10 m (room) 10 to 50 m; long-range modes more 10 to 50 m (line of sight) 4 cm (NFC) to 10+ m (UHF) Whatever protocol you flash
Distance accuracy Poor (RSSI) Poor (RSSI); better with AoA About 10 cm (ToF) In field or not; not a tape measure N/A
Tag / device power Battery, hours of audio Coin cell, months to years Battery; ranging costs more than BLE advertise Often none (passive) The MCU plus radio current
Cost of the "tag" Whole gadget A few dollars Higher (special chip + antenna) Cents to a dollar (passive) Chip price, not a tag
Phone support Universal Universal Flagships (Apple, Samsung, Google, and growing) NFC only on most phones; UHF needs a reader Inside many BLE gadgets, not the phone itself
Pick by the constraint you cannot break Need years on a coin cell BLE or passive RFID UWB and Classic drain faster nRF52-class SoC is typical for BLE Need true centimeters UWB BLE RSSI will lie in a metal room Often pair UWB with BLE wake-up Need a 10-cent ID Passive RFID / NFC No battery, no app required Needs a reader at the door Need music or a fat pipe Bluetooth Classic (or Wi-Fi) BLE can carry data. It is not a headset radio. Need to ship a BLE gadget nRF (or similar SoC) Protocol = BLE. Part number = nRF52840, nRF54L…

Each One, With a Real Example

Bluetooth Classic: the headset

You pair AirPods-class buds or a car stereo. The radio stays up and moves audio for hours. Classic Bluetooth (BR/EDR) was built for that continuous link. Putting the same job on BLE is possible in later specs, but most cars and speakers still speak Classic for audio.

Use when: the user hears or sends a stream. Do not use when: you need a five-year battery on a sticker.

BLE: the sensor and the "hello"

A heart-rate strap, a temperature logger, or a supermarket beacon advertises every second. A phone app connects, reads a few bytes, disconnects. BLE was designed for that duty cycle. Almost every smartphone can talk to it. Distance from signal strength is a guess: walk behind a fridge and "3 meters" becomes "12 meters."

Use when: phones must see you, power is tight, data is small. Do not use when: a forklift must stop at 1.5 m, not "somewhere nearby."

UWB: the tape measure

A digital car key measures time of flight. A relay thief in the street cannot make the radio wave travel faster than light, so the car stays locked. An iPhone draws an arrow to an AirTag because UWB gives distance and angle, not just "nearby." IEEE 802.15.4z is the secure-ranging standard behind most phones and cars (IEEE, 2020).

Use when: centimeters and anti-relay matter. Do not use when: you need a 5-cent tag on every carton.

RFID: the nametag

A warehouse portal reads a hundred UHF tags on a pallet as it rolls through. A badge on a lanyard opens a door at 13.56 MHz. A cow ear tag at 134 kHz survives mud. The tag is often a coil and a chip with no battery. The reader supplies the energy. RFID answers "who is this?" It does not play a podcast or report live GPS.

Use when: you must identify many cheap things, or tap a card. Do not use when: the thing must call a cloud API every minute with no reader nearby.

nRF: the board you design

A product spec says "BLE sensor, 2 years, over-the-air updates." The engineer picks an nRF52840 or nRF54 series part from Nordic Semiconductor, writes Zephyr or nRF Connect SDK firmware, and ships BLE. Some nRF parts include NFC for tap-to-pair. nRF is not competing with UWB as a standard. Nordic is a silicon vendor. Qorvo, NXP, and others make the UWB chips. You can put both on one board.

Use when: you are building the gadget. Do not say: "we will use nRF instead of BLE." That sentence does not parse.

Use-Case Chooser

If the user need is… use this Need Pick Example Wireless headphones in a car Bluetooth Classic Car stereo, earbuds App talks to a battery sensor BLE (+ nRF SoC) Glucose, bike cadence Phone as a secure car key UWB + BLE CCC Digital Key Arrow to a lost item UWB + BLE AirTag, SmartTag Office door badge HF RFID / NFC MIFARE, employee card Count cartons at a dock door UHF RFID Pallet portal Stop a forklift at 2 meters UWB RTLS Worker badge + vehicle Pay or tap-to-pair NFC (HF RFID) Transit card, tap earbuds Ship your own BLE widget nRF (or peer SoC) Custom sensor PCB Retail aisle "nearby" ads BLE beacon iBeacon / Eddystone

How Products Combine Them

One product, several radios Phone as car key BLE: wake and pair UWB: prove distance NFC: backup tap BLE alone is relay-attack food. UWB is the lock. BLE is the doorbell. nRF is not in the phone. Warehouse UHF RFID: carton ID UWB: people and trucks BLE: handheld scanners Do not track pallets with UWB tags if RFID already IDs them. Do not stop forklifts with RSSI. Your BLE gadget nRF SoC on the PCB Firmware speaks BLE Optional NFC tap-to-pair Add a UWB IC only if you must measure centimeters. That IC is usually not nRF.

Real Use Cases (Problem → Cause → Effect)

1. Office access with phones only

Problem: Staff lose plastic cards. Security wants phone unlock.

Cause: RFID cards are cheap but they are extra plastic. BLE "nearby" unlocks the door from the sidewalk.

Effect: Keep RFID for visitors and backups. For phones, use BLE to wake and UWB (or a tight NFC tap) to prove the person is at the reader, not in the parking lot.

2. Lost keys in a house

Problem: A BLE-only tag says "nearby." You still search for ten minutes.

Cause: RSSI cannot point. Walls change the number.

Effect: BLE finds the room. UWB draws the last-meter arrow. That is why finder tags added UWB.

3. Retail inventory

Problem: A store wants to know which jackets are on which rack.

Cause: Putting a BLE or UWB battery in every garment is cost and waste.

Effect: Sew a UHF RFID inlay. Walk a handheld reader. Count a thousand items. Use BLE only on the scanner, maybe on an nRF board.

4. "We specified nRF for location"

Problem: A spec sheet lists nRF as the location technology.

Cause: The team named the chip, not the measurement method. nRF running BLE still uses RSSI unless you add AoA hardware or a UWB chip.

Effect: Rewrite the spec: protocol first (BLE vs UWB vs RFID), then pick silicon (nRF, Qorvo, Impinj, NXP).

A Simple Decision Rule

  1. If the thing has no battery and you only need an ID, use RFID (NFC if a phone must tap).
  2. If a phone app must talk cheaply for years, use BLE. Build it on nRF or a peer SoC.
  3. If a human must hear a stream, use Bluetooth Classic.
  4. If you must prove distance or point at the thing, add UWB. Keep BLE for discovery.
  5. Never treat nRF as a substitute for UWB or RFID. It is the engine, not the road.

Bluetooth Classic moves sound. BLE moves small data on a diet. UWB measures time so distance is real. RFID names cheap things, often with no battery. nRF is Nordic's SoC that usually speaks BLE.

They are the same only at the slogan level: short-range wireless. They differ in physics, power, cost, and what question they can answer. Pick the question first. Then pick the radio. Then pick the chip.

References

  • Bluetooth SIG. Bluetooth Core Specification (Classic and Low Energy). https://www.bluetooth.com/specifications/specs/
  • IEEE. (2020). IEEE 802.15.4z-2020: Enhanced ultra wideband physical layers and associated ranging techniques. IEEE Standards Association.
  • ISO/IEC 18000 and ISO/IEC 14443. RFID and proximity-card (NFC) air interfaces.
  • Nordic Semiconductor. nRF52, nRF53, and nRF54 series product pages. https://www.nordicsemi.com/
  • GS1. EPC UHF Gen2 for item-level RFID. https://www.gs1.org/
Subscribe to: Posts (Atom)