3.4. Data storage format U.K.
3.4.1 Introduction U.K.
DDP_040The downloaded data has to be stored according to the following conditions:U.K.
The data shall be stored transparent. This means that the order of the bytes as well as the order of the bits inside the byte that are transferred from the card has to be preserved during storage.
All files of the card downloaded within a download session are stored in one file on the ESM.
3.4.2 File format U.K.
DDP_041The file format is a concatenation of several TLV objects.U.K.
DDP_042The tag for an EF shall be the FID plus the appendix „00“.U.K.
DDP_043The tag of an EF's signature shall be the FID of the file plus the appendix „01“.U.K.
DDP_044The length is a two byte value. The value defines the number of bytes in the value field. The value „FF FF“ in the length field is reserved for future use.U.K.
DDP_045When a file is not downloaded nothing related to the file shall be stored (no tag and no zero length).U.K.
[F1DDP_046 A signature shall be stored as the next TLV object directly after the TLV object that contains the data of the file. U.K.
| Definition | Meaning | Length |
|---|---|---|
| FID (2 Bytes) || ‘ 00 ’ | Tag for EF (FID) in the  or for common information of the card | 3 Bytes |
| FID (2 Bytes) || ‘ 01 ’ | Tag for Signature of EF (FID) in the  DF | 3 Bytes |
| FID (2 Bytes) || ‘ 02 ’ | Tag for EF (FID) in the  DF | 3 Bytes |
| FID (2 Bytes) || ‘ 03 ’ | Tag for Signature of EF (FID) in the  DF | 3 Bytes |
| xx xx | Length of Value field | 2 Bytes |
Example of data in a download file on an ESM:
Textual Amendments