Content for ETSI TS 102 221 PDF version: 17.1.0

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…

L.1 Examples of SET DATA and RETRIEVE DATA usage L.2 Examples of RETRIEVE DATA usage with transport protocol T = 0

L Examples of SET DATA and RETRIEVE DATA usage p. 181

L.1 Examples of SET DATA and RETRIEVE DATA usage p. 181

This clause describes the sequences on APDU level, i.e. C-APDUs are given as:

CLA INS P1 P2 {Lc DATA} {Le}.

The presence of components enclosed in {…} depends on the case of the APDU.

The terminal stores some data in the object with tag 'A1' of length 45 kB with interruption, good case.

Table L.1.1: SET DATA with interruption, good case

The terminal stores some data in the object with tag 'A1' of length 45 kB with interruption, error case.

Table L.1.2: SET DATA with interruption, error case

As a result of the error, the object with tag 'A1' is removed from the file.

The terminal retrieved the object with tag 'A2' with interruption (good case).

Table L.1.3: RETRIEVE DATA with interruption, good case

L.2 Examples of RETRIEVE DATA usage with transport protocol T = 0 p. 182

This clause describes the sequences on APDU and TPDU level.

C-APDUs are given as:

CLA INS P1 P2 {Lc DATA} {Le}

C-TPDUs are given as:

CLA INS P1 P2 P3 {DATA}

The presence of components enclosed in {…} depends on the case of the APDU or the type of the TPDU.

This clause gives examples of the usage of the RETRIVE DATA command with transport protocol T = 0. The first example is based on the preconditions out of Table L.1.3. Furthermore it is assumed that for the last block of the RETRIEVE DATA command only 64 additional data bytes are left to be retrieved to show the handling with the procedure byte '6C'. The second example shows the use of procedure byte '61' when a short object is retrieved.

Table L.2.1: RETRIEVE DATA with interruption, good case

Table L.2.2: RETRIEVE DATA, short object