Which bodies standardize NFC, and what each standard actually governs

01 / FIELD NOTE

Keep the decision tied to the operating context.

NFC is standardized by several bodies because it sits at the intersection of radio, smart cards and mobile telephony. Each organization owns a layer: ECMA writes the interface and protocol, ISO adopts and publishes the same work under its own numbers, ETSI carries it into the mobile network, and the NFC Forum defines what an application actually sees — tag types, data formats and operating modes. The result is that one technology is specified four times, and each specification governs something different.

The radio and protocol core is ECMA-340, the Near Field Communication Interface and Protocol, written by ECMA as a private standardization body and adopted by ISO as ISO/IEC 18092. ECMA-340 defines the RF field, initialization and anti-collision, the transport protocols, the active and passive radio modes and the peer-to-peer mode, and lists the data rates the interface supports. Standardization here is about making two devices meet in the air: what the field looks like, how a device finds another device, and how the data transfer is carried out.

The layer above the air is ECMA-352, the interface and protocol that selects the operating mode — whether a device behaves as a proximity card, a vicinity card or an NFC peer. At that level the standard is about choice: the device reads the environment and decides which protocol family it is speaking. ECMA-356 and ECMA-362 cover the test methods, the RF-interface conformance and the protocol conformance, while ISO publishes the same work as ISO/IEC 22536 and ISO/IEC 23917. Test methods matter because interoperability is the promise — two devices that meet the same test should work together.

The card side of NFC lives in the smart-card standards. ISO/IEC 14443 governs the RFID proximity cards that NFC can emulate or read, in four parts covering RF interface, activation and protocol, and ISO/IEC 15693 covers the vicinity cards with a longer range. These two define the physical and protocol behaviour of the cards a phone, a door or a reader interacts with. ETSI takes the same core into the mobile network: ETSI TS 102 190 is its adoption of ECMA-340 for mobile phones.

The NFC Forum occupies the application layer. It is an industry alliance whose job is to turn the radio and card protocols into specifications developers can build against: the Digital Protocol, the Activity and Analog specifications, the NFC-Controller Interface (NCI), data-exchange formats, the record-type definitions, and the five NFC Forum tag types that make a physical tag addressable in a standard way. The Forum also runs conformance so that a product claiming NFC support actually does what the specification says.

Connection handover is the specification that makes NFC a pairing bridge rather than an end. A device uses NFC to carry a handover message that selects an alternate carrier — Bluetooth or Wi-Fi — and negotiates the connection: static handover presents the carrier choice in a record, negotiated handover uses the peer-to-peer link to agree on a carrier. The standard defines the three actions: select the carrier, connect to it under its own standard, and act per its own protocol. The tap is the door; the handover is the door opening onto another radio technology.

Two bodies govern what is inside the device rather than in the air. The SIM-side interface between the card and the NFC chipset is specified by ETSI in the Smart Card Platform work, and the secure element’s multi-application architecture, with over-the-air provisioning, is specified by GlobalPlatform; EMVCo carries the impact on payment applications. The lesson of the whole stack is that NFC security and behaviour are not one standard but a chain of custody among bodies — the interface is defined three times, the card twice, the application once, and each layer trusts the one below it.

The honest limit of this map is that it describes the standards, not the field. A specification states the normative behaviour; real deployments still depend on antenna tuning, on the coupling physics of a given phone and on the exact tag that was shipped. What the standards provide is the boundary within which the physics is expected to behave — and the conformance regime that lets a developer assume the person’s phone will do what the next phone does, which is the property a consumer-facing technology cannot live without.