ISO/IEC 7816-4
Identification cards — Integrated circuit cards — Part 4: Organization, security and commands for interchange
Cartes d’identification — Cartes à circuit intégré — Partie 4: Organisation, sécurité et commandes pour les échanges

 Short EF identifier
The following rules apply for the use of tag ’88′ in the control parameters of any EF.
–If the card supports selection by short EF identifiers (see 5.3.1.1) and if tag ’88′ is absent, then in the second byte of the file identifier (tag ’83′), bits 5 to 1 encode the short EF identifier.
–If tag ’88′ is present with a length set to zero, then the EF supports no short identifier.
–If tag ’88′ is present with a length set to one and if bits 8 to 4 of the data element are not all equal and if bits 3 to 1 are set to 000, then bits 8 to 4 encode the short EF identifier (a number from one to thirty).

Life cycle status byte
The card, files and other objects, each have a life cycle; the life cycle status allows the card and the interface device to identify the different logical security states of the use of the card, files and other objects in the card.
To support flexible management of the life cycle as an attribute (see ISO/IEC 7816-9[4]), this clause defines four primary states of the life cycle in the following order.
1) Creation state
2) Initialisation state
3) Operational state
4) Termination state
The life cycle status byte (LCS byte) shall be interpreted according to Table 13.
–The values ’00′ to ’0F’ are interindustry.
–The values ’10′ to ‘FF’ are proprietary.  

Table 13 Life cycle status byte
b8 b7 b6 b5 b4 b3 b2 b1 Meaning
0 0 0 0 0 0 0 0 No information given
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1 0 1 -1 0 1 -0 1 1 – Creation state Initialisation state Operational state (activated) Operational state (deactivated) Termination state
Not all zero x x x x Proprietary
Any other value is reserved for future use by ISO/IEC JTC 1/SC 17.

  Referenced by tag ’8A’, a file LCS byte may be present in the control parameters of any file (see Table 12).
A card LCS byte may be present in the historical bytes (see 8.1.1.3). Referenced by tag ’48′, a card LCS byte may be present in EF.ATR (see 8.2.1.1). When it has a MF, the card is in, at least, the creation state.
NOTE Unless otherwise specified, the security attributes are valid for the operational state.

File descriptor byte
Referenced by tag ’82′, a data element may be present in the control parameters of any file (see Table 12).
–The first byte of the data element is the file descriptor byte (see Table 14).
–If the data element consists of two or more bytes, then the second byte is the data coding byte (see Table 87). If the card provides data coding bytes in several places, then the indication valid for a given file is in the closest position to that file within the path from the MF to that file.

Table 14 — File descriptor byte
b8 b7 b6 b5 b4 b3 b2 b1 Meaning
0 0 0 x 0 1 ——— ——— File accessibility —Not shareable file —Shareable file
0 - 1 1 1 0 0 0 DF
0 - Not all set to 1 EF category
0 - 0 0 0 —Working EF
0 - 0 0 1 —Internal EF
0 - Any other value —Proprietary categories of EFs
0 -     EF structure
0 - Not all set to 1 0 0 0 —No information given
0 - Not all set to 1 0 0 1 —Transparent structure
0 - Not all set to 1 0 1 0 —Linear structure, fixed size, no further information
0 - Not all set to 1 0 1 1 —Linear structure, fixed size, TLV structure
0 - Not all set to 1 1 0 0 —Linear structure, variable size, no further information
0 - Not all set to 1 1 0 1 —Linear structure, variable size, TLV structure
0 - Not all set to 1 1 1 0 —Cyclic structure, fixed size, no further information
0 - Not all set to 1 1 1 1 —Cyclic structure, fixed size, TLV structure
0 - 1 1 1 0 0 1 —TLV structure for BER-TLVdata objects
0 - 1 1 1 0 1 0 —TLV structure for SIMPLE-TLVdata objects
 Any other value is reserved for future use by ISO/IEC JTC 1/SC 17.

 “Shareable”means that the file supports at least concurrent access on different logical channels.