T=1

Protocole
{# Answer-first lead — frontend-gold-standard §1.1. Expects `lead` (plain text, already resolved by apps.content.leads). Rendered directly under the h1 so the self-contained answer is the first prose a reader, a SERP snippet, or an AI extractor meets. No curated-data gate: the view always supplies either curated content_summary or a computed fallback. #}

Block-oriented transmission protocol for contact smart cards defined in ISO 7816-3. It is also written T=1 protocol. The term belongs to the Protocole section of the smart card glossary.

Embed This Widget

Theme


      
    

Widget powered by . Free, no account required.

Also known as: T=1 protocol

T=1

T=1 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 14443-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 APDU 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.

{# FAQ block + FAQPage JSON-LD. Expects `faq_items` = [{"question", "answer"}]. Native
/ (frontend-gold-standard §1.7): the answer text is in the initial HTML and stays reachable with JavaScript disabled, so crawlers and AI extractors read answer-shaped chunks without depending on Alpine. #}

Frequently Asked Questions

What fields make up a T=1 block?

Each block carries a one-byte NAD identifying source and destination nodes, a one-byte PCB giving block type and sequence number, a one-byte LEN, an information field of 0 to 254 bytes, and an error detection code of one byte as an LRC or two bytes as a CRC-16.

What are I-blocks, R-blocks, and S-blocks?

The PCB distinguishes three block types. I-blocks carry application data, R-blocks acknowledge reception and request retransmission, and S-blocks handle protocol-level control such as resynchronisation, information field size negotiation, and waiting time extension.

How does T=1 handle an APDU larger than one block?

Chaining segments the APDU across multiple I-blocks when it exceeds the maximum information field size — IFSC for the card, IFSD for the reader. The more-data bit in the PCB indicates whether further blocks follow.

Where else is T=1 used besides contact cards?

The block structure of T=1 is the basis for contactless communication under ISO 14443-4, which is why the protocol appears in both contact and contactless stacks.

What is the smart card glossary and who is it for?

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.

Are the glossary definitions available in other languages?

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.