IEC 14443-3:2018 – Initialization and Anticollision for Proximity Cards

Technical overview of contactless card initialization, anticollision protocols, and compliance

ISO/IEC 14443-3:2018 (also adopted as CAN/CSA-ISO/IEC 14443-3:18 and widely referred to as IEC 14443-3:2018) is the third part of the ISO/IEC 14443 series, which defines the physical and protocol characteristics of proximity cards (PICCs) and proximity coupling devices (PCDs). This standard specifies the initialization, anticollision, and selection protocols that enable a PCD to communicate with one or more PICCs in a contactless environment. It is fundamental to contactless smart card systems, NFC applications, and secure identification solutions.

1. Scope of IEC 14443-3:2018

The standard covers the data link layer of the contactless interface, specifically:

  • Initialization procedures for the PCD to detect and activate PICCs entering the electromagnetic field.
  • Anticollision protocols for managing multiple PICCs in the field and isolating a single card for subsequent transactions.
  • Command sets, frame structures, and timing parameters for both Type A and Type B communication interfaces.
  • Procedures for card selection, halt, and wake-up commands.

It applies to Proximity Integrated Circuit Cards (PICCs) operating at 13.56 MHz and the corresponding PCDs. The standard ensures interoperability between devices from different manufacturers, independent of higher‑layer applications.

Tip: IEC 14443-3:2018 is the direct successor to the 2011 edition. Key changes include clarified timing boundaries for Type A and an optional enhanced anticollision sequence for Type B.

2. Technical Requirements and Frame Format

2.1 Frame Structure

All communication is based on frames that include a start bit, data bits (typically 8 bits per byte), an optional parity bit per byte, and an end bit. The standard defines two fundamental frame types:

  • Short Frame – 7 data bits, used for initial requests (REQA, WUPA).
  • Standard Frame – variable length (multiple bytes), used for commands and responses.

2.2 Command Summary

Command Code (Type A) Code (Type B) Description
REQA 0x26 Request for Type A card presence
WUPA 0x52 Wake-up of Type A card
ANTICOLLISION 0x93 / 0x95 / 0x97 0x1D Collision resolution cascade
SELECT 0x93 / 0x95 / 0x97 (with SEL code) 0x0D Card selection by full UID
HLTA 0x50 0x10 (HALT) Halt command to deselect card

2.3 Timing Parameters

The standard defines several time intervals that must be respected to maintain reliable communication:

  • T0 – Guard time after a response (min. 120 μs for Type A, 20 μs for Type B).
  • T1 – PCD frame delay (typically 86 μs for Type A, 100 μs for Type B after a card response).
  • T2 – Timeout for card response (max. 5 ms, Type A; 2.26 ms, Type B).
  • T4, T5, T6 – Additional recovery and processing times specific to Type A and B.
Warning: Timing violations are a common source of interoperability problems. Designers should thoroughly validate all time intervals under worst-case loading conditions (e.g., many cards in field, low coupling).

2.4 Anticollision Mechanism

For Type A, a binary search tree anticollision method is used, based on the unique identifier (UID) length of 4, 7, or 10 bytes. The PCD sends cascaded anticollision loops, and each PICC responds with its UID bits. Collisions are detected at the bit level, and the PCD isolates one card by selecting a unique UID. Type B uses a slotted ALOHA approach, where cards pick a random slot and transmit their UID if no collision occurs. The standard specifies both mechanisms in detail to ensure deterministic behavior.

3. Implementation Highlights for Contactless Systems

When implementing a PCD (reader) or PICC (card) compliant with IEC 14443-3:2018, the following aspects deserve special attention:

3.1 Type A vs Type B Interoperability

A PCD must support at least one interface type. Dual‑interface readers often implement both Type A and Type B sequentially. The initialization procedure for Type A begins with REQA at a fixed bit rate (106 kbps), while Type B starts with a request using a different framing and code. The standard does not require simultaneous support, but most commercial readers offer both.

3.2 Collision Detection and Resolution

Robust collision detection requires precise bit sampling. For Type A, the PCD must be able to detect the difference between an explicit bit (0 or 1) and a collision (both 0 and 1 received). This is usually handled by the analog front‑end and decoder logic. For Type B, the PCD must detect slot start times and handle multiple responses. Special care must be taken to avoid false collisions due to noise or weak coupling.

3.3 Power and Field Stability

During the anticollision phase, the PCD may need to adjust the RF field strength to guarantee that all PICCs are powered correctly. The standard recommends that the field remain active throughout the entire initialization sequence, and any momentary interruptions (e.g., due to load modulation) must be within specified recovery times.

Success: Compliant readers that strictly follow the frame timing and collision resolution procedures of IEC 14443-3:2018 achieve a card selection success rate > 99.9% in mixed populations of Type A and Type B cards.

4. Compliance and Conformance Testing

To claim compliance with IEC 14443-3:2018, products must undergo conformance testing that covers:

  • Physical layer parameters (carrier frequency, modulation depth, bit encoding).
  • Protocol conformance: correct frame sequences, CRC, parity, and timing.
  • Anticollision behavior under single‑card and multi‑card scenarios.
  • Error handling: invalid commands, timeouts, and collision resolution.

4.1 Test Tools and Reference Devices

Conformance is typically verified using a dedicated test platform (e.g., a reference PCD) that simulates all required protocol sequences. The standard references ISO/IEC 10373-6 for test methods for proximity cards. Additionally, the GlobalPlatform and NFC Forum test suites include IEC 14443-3 conformance sections.

4.2 Certification Mark

Products that pass accredited testing laboratories can be certified under the IEC System of Conformity Assessment Schemes (IECEE). For the Canadian adoption (CAN/CSA-ISO/IEC 14443-3:18), certification may be required for usage in regulated identification systems.

Danger: Non‑compliance with timing parameters, especially T0 and T2, can cause intermittent communication failures and make a device unsuitable for multi‑vendor environments. Always test with multiple card types and fields strengths.


Q: What is the difference between ISO/IEC 14443-3:2018 and the older 2011 edition?
A: The 2018 edition clarifies timing thresholds for Type A, introduces an enhanced anticollision cascade for Type B, and updates references. It also harmonizes with later amendments related to NFC‑A and NFC‑B protocols.
Q: Does this standard apply to both Type A and Type B simultaneously?
A: No, the standard describes both protocols separately. A PCD may support either Type A, Type B, or both. Dual‑interface readers typically switch between the two during initialization.
Q: Is IEC 14443-3:2018 equivalent to CAN/CSA-ISO/IEC 14443-3:18?
A: Yes, the Canadian standard is an identical adoption of the international standard. All technical requirements and test methods are the same.
Q: What is the maximum number of cards that can be handled during anticollision?
A: For Type A, up to 16 cards per cascade level (theoretical maximum). In practice, the PCD can handle over 100 cards with appropriate timing and field management, though higher layers (e.g., ISO/IEC 14443-4) may impose limits.


Technical reference material prepared 2026. This article is for informational purposes and does not replace the official standard text.

📥 Standard Documents Download

🔒
Please wait 10 seconds, the download links will appear after the ad loads

Leave a Reply

Your email address will not be published. Required fields are marked *