T=1
ProtocolBlock-oriented transmission protocol for contact smart cards defined in ISO 7816-3.
T=1
T=1T=1ProtocolBlock-oriented smart card protocol.Click to view → is a block-oriented transmission protocol for contact smart cards, defined in ISO 7816 Part 3. It provides framed data transfer with built-in error detection and block-level retransmission, making it the preferred protocol for high-throughput applications and the basis for contactless communication under ISO 14443ISO 14443StandardStandard for contactless smart cards.Click to view →-4.
Block Structure
Every T=1 exchange is encapsulated in a block with a well-defined header and trailer:
| Field | Length | Description |
|---|---|---|
| NAD | 1 byte | Node address — source and destination identifiers |
| PCB | 1 byte | Protocol control byte — block type and sequence number |
| LEN | 1 byte | Length of the information field (0-254) |
| INF | 0-254 bytes | APDU data (partial or complete) |
| EDC | 1-2 bytes | Error detection code — LRC (1 byte) or CRC-16 (2 bytes) |
T=1 defines three block types through the PCB byte: I-blocks carry application data, R-blocks acknowledge reception and request retransmission, and S-blocks handle protocol-level control such as resynchronization, interface field size negotiation, and waiting time extension.
Chaining
When an APDUAPDUProtocolCommunication unit between card and reader.Click to view → exceeds the maximum information field size (IFSC for card, IFSD for reader), T=1 segments it into multiple I-blocks using the chaining mechanism. The M-bit (more data) in the PCB indicates whether additional blocks follow. This allows large data transfers — such as reading a certificate or downloading a JavaCard applet — without size limitations at the protocol level.
Error Handling
T=1 uses block-level error recovery. If the EDC check fails, the receiver sends an R-block requesting retransmission of the erroneous block. If retransmission fails repeatedly, either party can request a resynchronization via an S-block, which resets sequence counters without a full card reset. This makes T=1 more resilient than T=0 for noisy contact interfaces.
Relationship to Contactless
ISO 14443-4 adopted the T=1 framing concept for contactless smart card communication. The contactless transport protocol uses essentially the same block structure (I-block, R-block, S-block) but replaces the byte-level electrical signaling with RF modulation. This architectural alignment means that application code written against a T=1 stack typically works over contactless with minimal modification — a key design goal for dual-interface modules.
Related Content
Smart Card Fundamentals
Getting Started…— a byte string that announces supported protocols ( T=0 , T=1 ), clock frequency, and optional historical bytes. Parse…
Contact vs Contactless vs Dual-Interface
Getting Started…ISO 14443 transport framing rather than the ISO 7816 T=0/T=1 byte stream. Dual-Interface Cards Dual-interface (DI)…
Smart Card Reader Setup Guide
Getting Started…Families Interface Standard Typical Use Cases Contact (T=0/T=1) ISO 7816-3 PKI tokens, PIV cards, JavaCard dev…
SIM Card Types Explained
Getting Started…general-purpose smart cards which may also negotiate T=1 . The ATR transmitted at power-on identifies voltage class…
Understanding ISO 7816
Standards & Protocols…info (issuer, card type) TCK — XOR checksum (present when T=1 is offered) The T=0 protocol is byte-oriented and…
ISO 14443 Deep Dive
Standards & Protocols…provides the same error-recovery semantics as ISO 7816 T=1 over the contactless channel. The APDU payload itself is…
ISO 7816 Parts Guide
Standards & Protocols…interface and transmission protocols ATR , T=0 , T=1 , PPS 7816-4 Organisation, security and commands File…
Post-Quantum Cryptography for Smart Cards
Security…smart cards. APDU Chaining for Large Objects Standard T=1 APDU data length is limited to 255 bytes (short form) or…
คำถามที่พบบ่อย
The smart card glossary is a comprehensive reference of technical terms, acronyms, and concepts used in smart card technology. It covers protocols (APDU, T=0, T=1), security (Common Criteria, EAL, HSM), hardware (SE, EEPROM, contact pad), and applications (EMV, ePassport, eSIM). It serves developers, product managers, and engineers.
Yes. SmartCardFYI provides glossary definitions in 15 languages including English, Korean, Japanese, Chinese, Spanish, Portuguese, Hindi, Arabic, French, Russian, German, Turkish, Vietnamese, Indonesian, and Thai.