STANDARD. ISO/IEC. Second edition. Identification cards — Integrated circuit cards —. Part 5: Registration of application providers. ISO is one of most important standards in the smart card industry. Parts of ISO specify physical characteristics, dimensions and location of the. ISO , Section 5 contains basic organizations, data structures, file organization, file referencing methods, data referencing methods, record referencing.
|Published (Last):||9 June 2005|
|PDF File Size:||9.29 Mb|
|ePub File Size:||14.48 Mb|
|Price:||Free* [*Free Regsitration Required]|
This part specifies commands for ios management in a multi-application environment. The length Le is also not null; therefore the Le field is also present.
Identification of persons using biometric methods is outside the scope of this standard. Each command message may carry a response descriptor template fixing the data objects required in response.
In order to select unambiguously by DF io e. Short EF identifiers connot be used in a path or as a file identifier e. Command-specific status — It only exists during the execution of a command involving authentication using secure messaging see 1. The data fields of some other commands e.
Enregistrement des fournisseurs d’application. The file control information may be present for any file. Your basket is empty. Commands for card management”. Linear EF with record of fixed size.
Created inamended in,updated in Views Read Edit View history. Click to learn more.
ISO – important industry standard for integrated circuit cards
The following structures of EFs are defined: The FCI template is intended for conveying file control parameters and file management data.
Each time a reference is made with a record identifier, an indication shall specify the logical position of the target record the first or last occurrence, the next or previous occurrence relative to the record pointer:.
Within each EF of transparent structure, each data unit can be referenced by an offset e. Created inupdated inamended in Iwo other projects Wikimedia Commons. The last possible position of a control reference template is just before the first data object to which the referred mechanism applies.
ISO part 4 section 5 APDU level data structures
There are two types of digital signatures: The first 4 cases apply to all cards. It may be maintained, recovered or lost by file selection see 6. Padding for confidentiality has an influence on transmission, the cryptogram one or more blocks is longer than the plain text. In the data field, the present SM format may be selected implicitly, i.
The following attributes are defined for EFs structured in records: Each data object as defined in 1. The length field consists of 1 or 3 consecutive bytes.
This part specifies the power, signal structures, and the structure for the answer to reset between an integrated circuit card s with synchronous transmission and an interface device such as a terminal. The blocking shall be continuous at the border between adjacent data objects to be integrated The padding shall apply at the end of each data object to be integrated followed either by a data object not to be integrated or by no further data object.
Within an EF of record structure, records may have the same record identifier, in io case data contained in the records may be used for discriminating between them.
In order to select unambiguously any file by its identifier, all EFs and DFs immediately under a given DF shall have different file identifiers. Created inupdated in Between those two identifiers, the path consists of 781-65 identifiers of the successive parent DFs if any.
The security attributes of file depend on:.
F I G U R E 2
Referencing by path — Any file may be referenced by a path concatentation of file identifiers. Data objects of the other classes may be present e. Concealment thus requires no padding and the data objects concealed in the value field are recovered by the same operation.