Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  ETSI TS 102 221   PDF version:  17.1.0

Top   Top   Up   Prev   Next
0…   4…   5…   6…   7…   7.3…   8…   9…   10…   10.2…   11…   11.1.2…   11.1.9…   11.1.14…   11.1.19…   11.1.20…   11.1.21…   11.2…   11.3…   12…   13…   14…   15   A   B   C…   D   E…   F…   G…   H…   I   J…   K…   L…   M…

 

C  APDU protocol transmission examplesp. 159

C.1  Exchanges Using T = 0p. 159

C.1.0  Overviewp. 159

The following examples illustrate exchanges of data and procedure bytes between the terminal and the UICC when standard logical channels are used (see clause 10.1.1).
Note the following:
  • The use of procedure bytes '60' and is not illustrated.
  • [Data(X)] means X bytes of data.
  • Case 2 and 4 commands may have Le = '00' requesting the return of all data from the UICC up to the maximum available.
The examples in clauses C.1.1 to C.1.4 illustrate typical exchanges using case 1 to 4 commands. The examples in the clauses C.1.5 and C.1.6 illustrate the more extensive use of procedure bytes '61 XX' when used with cases 2 and 4 commands. The example in clause C.1.7 illustrates a warning condition with a case 4 command.
Up

C.1.1  Case 1 commandp. 159

A C-APDU of {CLA INS P1 P2} is passed from the terminal to the UICC (note that P3 of the C-TPDU is set to '00').
Annex C - Case 1
An R-APDU of {90 00} is returned from the UICC to the terminal.

C.1.2  Case 2 commandp. 159

In this first example, a C-APDU of {CLA INS P1 P2 Le = 00} is passed from the terminal to the UICC with Luicc < 256 bytes.
Annex C - Case 2: Luicc < 256 bytes
An R-APDU of {[Data(Luicc)] 90 00} is returned from the UICC to the terminal.
In this second example, a C-APDU of {CLA INS P1 P2 Le = 00} is passed from the terminal to the UICC with Luicc = 256 bytes.
Annex C - Case 2: Luicc = 256 bytes
An R-APDU of {[Data(Luicc)] 90 00} is returned from the UICC to the terminal.
Up

C.1.3  Case 3 commandp. 160

A C-APDU of {CLA INS P1 P2 Lc [Data(Lc)]} is passed from the terminal to the UICC.
Annex C - Case 3
An R-APDU of {90 00} is returned from the UICC to the terminal.

C.1.4  Case 4 commandp. 160

A C-APDU of {CLA INS P1 P2 Lc [Data (Lc)] Le = 00} is passed from the terminal to the UICC.
Annex C - Case 4
An R-APDU of {[Data(Luicc)] 90 00} is returned from the UICC to the terminal.
The GET RESPONSE command is sent on the same logical channel as the C-TPDU.

C.1.5  Case 2 commands Using the '61' and '6C' procedure bytesp. 160

A C-APDU of {CLA INS P1 P2 Le = 00} is passed from the terminal to the UICC with Luicc < 256 bytes.
Annex C - Case 5
Where YY ≤ XX,
An R-APDU of {[Data(YY + ZZ)] 90 00} is returned from the UICC to the terminal.
The GET RESPONSE command is sent on the same logical channel as the C-TPDU.

C.1.6  Case 4 command Using the '61' procedure bytep. 161

A C-APDU of {CLA INS P1 P2 Lc [Data Lc] Le = 00} is passed from the terminal to the UICC.
Annex C - Case 6
An R-APDU of {[Data(XX + YY)] 90 00} is returned from the UICC to the terminal.
The GET RESPONSE command is sent on the same logical channel as the C-TPDU.

C.1.7  Case 4 command with warning conditionp. 161

A C-APDU of {CLA INS P1 P2 Lc [Data Lc] Le = 00} is passed from the terminal to the UICC.
Annex C - Case 7
An R-APDU of {[Data(Luicc)] 62 XX} is returned from the UICC to the terminal containing the data returned together with the warning status bytes.
The GET RESPONSE command is sent on the same logical channel as the C-TPDU.

Up   Top   ToC