Compare T=0 and T=1 protocols

[Papa Carder]

Overview of T=0 and T=1 Protocols​

T=0 and T=1 are transmission protocols defined in the ISO/IEC 7816 standard for smart cards (both contact and contactless interfaces). They govern how data is exchanged between the card and the reader in a half-duplex manner, building on the APDU (Application Protocol Data Unit) structure. These protocols handle framing, error detection, and flow control at the transport layer.

• T=0: A byte-oriented (character-oriented) protocol, primarily used in older or simpler smart cards. It transmits data one byte at a time and relies on procedure bytes for acknowledgment and error handling.
• T=1: A block-oriented protocol, designed for more reliable communication. It sends data in blocks with built-in error detection and correction mechanisms, making it suitable for environments prone to noise or errors.

Both protocols support the same APDU commands but differ in efficiency, error resilience, and implementation complexity. T=0 is mandatory for compliance with ISO/IEC 7816, while T=1 is optional but widely adopted in modern applications like EMV payment cards or ePassports.

Key Comparison​

Aspect	T=0 Protocol	T=1 Protocol
Orientation	Byte-oriented (transmits individual characters/bytes).	Block-oriented (transmits data in structured blocks).
Framing	No explicit frames; uses procedure bytes (e.g., ACK/NAK) sent by the card after each command byte to control flow.	Uses defined blocks: Prologue (NAD, PCB, LEN), Information (data), Epilogue (EDC for error detection, e.g., LRC or CRC).
Error Handling	Basic: Relies on parity bits per byte and procedure bytes for retransmission requests. Errors require resending the entire command.	Advanced: Includes error detection codes (EDC) in each block. Supports automatic retransmission and chaining for large data.
Flow Control	Half-duplex; card sends procedure bytes to indicate readiness (e.g., SW1=0x60 for time extension). Reader must poll for status.	Half-duplex with better chaining; uses Protocol Control Byte (PCB) for acknowledgments, chaining, and error signals.
Efficiency	Less efficient for large data transfers due to byte-by-byte acknowledgments, leading to higher overhead.	More efficient for bulk data; blocks can be up to 254 bytes, reducing overhead in noisy or high-volume scenarios.
Complexity	Simpler to implement; common in legacy systems like early SIM cards or basic ID cards.	More complex but robust; preferred in secure applications like banking (EMV) or government IDs.
Data Rate Support	Supports standard rates but limited by byte-level processing.	Better suited for higher speeds; can handle variable bit rates more effectively.
Compatibility	Mandatory in ISO/IEC 7816; fallback protocol if T=1 negotiation fails.	Optional; negotiated during Answer to Reset (ATR) phase. Cards may support both.
Use Cases	Older telephony cards (e.g., GSM SIM), simple authentication tokens.	Modern payment cards (EMV), ePassports (ICAO), secure elements in NFC devices.
Limitations	Prone to errors in noisy environments; no built-in CRC, so higher retry rates.	Higher implementation cost; not backward-compatible without T=0 fallback.

Negotiation and Setup​

During the card's activation (e.g., via Reset or PPS - Protocol and Parameters Selection), the Answer to Reset (ATR) message indicates supported protocols. The TA1 byte in ATR specifies interface parameters, and the reader can propose switching from default T=0 to T=1 if both support it. If negotiation fails, it defaults to T=0.

Secure Messaging Integration​

Both protocols can incorporate Secure Messaging (SM) as per ISO/IEC 7816-4, wrapping APDUs with encryption and MACs. However, T=1's block structure makes SM more seamless for chained commands, reducing the risk of partial transmissions in secure sessions.

In practice, many contactless systems (e.g., ISO/IEC 14443) use a variant called T=CL (Contactless), which adapts elements from T=1 for wireless environments but isn't directly T=0 or T=1.

For detailed specifications, refer to ISO/IEC 7816-3 (electrical interface and transmission protocols). If implementing, T=1 is recommended for new designs due to its reliability.