44 ETSI TS 102 221 V17.1.

0 (2022-02)

The value of CWT may be calculated from the following equation: CWT = (11 + 2CWI) etu.

7.2.3.1.4 Block waiting time

BWT is defined as the maximum delay between the leading edge of the last character of the block received by the card
and the leading edge of the first character of the next block sent by the card.

<- Last character of a block sent by the

terminal

First character of next block sent by the UICC ->

BWT

Figure 7.4: Block waiting time

BWT is used to detect an unresponsive card.

7.2.3.1.5 Block guard time

BGT is defined as the minimum delay between the leading edge of two consecutive characters sent in opposite
directions. The value of BGT shall be 22 etu.

<- Last character of a block sent by the

terminal

First character of next block sent by the UICC ->

BGT

Figure 7.5: Block guard time

The delay between the last character of a block received by the UICC and the first character of the next block sent from
the UICC shall be in the interval:

• BGT < delay < BWT.

7.2.3.1.6 Waiting time extension

WTX is a parameter used to ask for more time to process a command.

7.2.3.1.7 Error detection code

The parameter tCi in the ATR is used to define which error detection code to use. LRC shall be used (b1 = 0). All other
bits in tCi are RFU and shall be set to 0.

7.2.3.2 Block frame structure

7.2.3.2.0 Overall structure

The protocol consists of blocks, which are transmitted between the terminal and the UICC. Each block has the
following structure.

Table 7.3: Block frame structure

Prologue field Information field Epilogue field
NAD PCB LEN INF EDC
1 byte 1 byte 1 byte 0 byte to 254 bytes 1 byte

The prologue field and the epilogue field are mandatory. The Information field is optional.

ETSI
 45 ETSI TS 102 221 V17.1.0 (2022-02)

7.2.3.2.1 Prologue field

7.2.3.2.1.0 Field Structure

The prologue field is divided into the following three mandatory fields:

• Node ADdress byte (NAD), 1 byte;

• Protocol Control Byte (PCB), 1 byte;

• LENgth (LEN), 1 byte.

7.2.3.2.1.1 Node address byte

The NAD-byte identifies the source and the intended destination of the block. The NAD may also be used to distinguish
between different logical connections if they coexist as well as to provide Vpp state control (bit b8 and b4). Since b8
and b4 are not used, they shall be coded as '0'. Below is the structure of the NAD-byte.

Table 7.4: Node address byte

b8 b7 b6 b5 b4 b3 b2 b1
Unused DAD Unused SAD

In the first block sent from the terminal, a logical connection is set up based on the addresses in SAD and DAD.
Subsequent blocks with an NAD containing the same pair of addresses are associated with the same logical connection.

Only the default value SAD = DAD = 0 shall be supported. All other combinations are RFU.

7.2.3.2.1.2 Protocol Control Byte

All information needed to control the transmission is transferred in the protocol control byte PCB. The coding of the
PCB specifies the type of block. In the T = 1 protocol the following three different types of blocks are supported:

• Information block (I-block): which is used to transfer command and response APDUs;

• Receive-ready block (R-block): which is used to transfer acknowledgements;

• Supervisory block (S-block): which is used to send control information.

Tables 7.5 to 7.9 present the coding of the PCB for each block-type, starting with the I-block.

Table 7.5: Coding of PCB for an I-block

b8 b7 b6 b5 b4 b3 b2 b1
Sequence Chaining,
0 number, more-data RFU
N(S) bit, M

Table 7.6: Coding of PCB for an R-block

b8 b7 b6 b5 b4 b3 b2 b1
Sequence
1 0 0 See table 7.7
number N(R)

ETSI
 46 ETSI TS 102 221 V17.1.0 (2022-02)

Table 7.7: Bit b4 to b1 in the PCB for the R-block

b4 b3 b2 b1 Value Meaning
0 0 0 0 '0' Error free
0 0 0 1 '1' EDC and/or parity error
0 0 1 0 '2' Other errors
X X X X 'X' Other values are RFU

Table 7.8: Coding of PCB for an S-block

b8 b7 b6 b5 b4 b3 b2 b1
1 1 X See table 7.9

Table 7.9: Bits b5 to b1 of PCB for an S-block

b5 b4 b3 b2 b1 Value Meaning
0 0 0 0 0 '0' Resynchronization
0 0 0 0 1 '1' Information field
0 0 0 1 0 '2' Abortion
0 0 0 1 1 '3' Extension of BWT
0 0 1 0 0 '4' Error on VPP State (see note)
X X X X X 'X' Other values are RFU
NOTE: Not used by UICCs and terminals conforming to the present document.

The coding of b6 indicates whether it is a request (b6 = 0) or a response (b6 = 1).

7.2.3.2.1.3 Length

The length byte codes the number of bytes in the Information field of the block. The number of bytes in the information
field may vary in the range from 0 byte to 254 bytes, depending on the type of block.

The value LEN = '00' indicates that the information field is absent and the value 'FF' is RFU.

7.2.3.2.1.4 Information field

The information field, INF, is optional and it depends on the type of the block what the field will be used for.

Table 7.10: Information field

Type of block INF used for
I-block Transfer command and response APDUs.
R-block Not used.
Transfers non application related information:
• INF shall be present (single byte) to adjust IFS with WTX;
S-block
• INF shall be absent to signal error on VPP, or managing chain
abortion or resynchronization.

7.2.3.2.2 Epilogue field

The epilogue field contains the Error Detection Code-byte (EDC), which transfers the error detection code of the
transmitted block.

The LRC as defined in ISO/IEC 7816-3 [11] shall be used.

ETSI