← Back to the chapter

Technical detail · NFC Protocols: Handover Boundaries

Initiator, Target, and Passive Communication

14.4.1 Initiator, Target, and Passive Communication

Every NFC exchange has an initiator that starts and drives the exchange and a target that responds. In passive communication mode, only the initiator generates the 13.56 MHz field; the target replies by load modulation, varying how much energy it draws from the initiator field. This is the same operating idea that lets an unpowered HF RFID tag answer a reader.

This distinction explains several field failures. A phone can read an unpowered sticker because the phone is the initiator generating the field and the passive tag load-modulates a reply. At a cabinet reader or payment terminal, the fixed reader creates the field and sends commands; the phone acts as the card-emulation target and answers only through an allowed card application. Having a battery does not mean the phone owns the field.

Diagnose NFC failures from the bottom upward:

  1. No target reported: inspect field coupling, antenna orientation, tag technology support, shielding, mounting surface, and polling configuration.
  2. Target reported but no NDEF or APDU response: inspect activation, tag type mapping, memory access, ISO-DEP application selection, and record format.
  3. Payload parsed but action denied: inspect application policy, technician session, object state, authorization, and fallback.
  4. Handover tap succeeds but setup fails later: inspect peer identity, carrier pairing, session protection, timeout behavior, and rollback.

For card emulation, release evidence should record which application was selected, what happens when the reader asks for an unsupported application, whether user presence is required, and what audit event is emitted for declined or ambiguous taps. A successful “phone seen by reader” test can still hide a credential-policy failure.

← Back to the chapter