ISO/IEC is intended to be used in any sector of activity. It specifies: a ) contents of command-response pairs exchanged at the interface,. b) means of. ISO , Section 5 contains basic organizations, data structures, file organization, file referencing methods, data referencing methods, This part of ISO/IEC supports the following two categories of files: . 0 — x x x — — —, File type. ISO/IEC (): “Information technology – Identification cards; Integrated circuit(s) cards . and one or more SC bytes as defined in ISO/IEC .
|Published (Last):||25 January 2014|
|PDF File Size:||5.38 Mb|
|ePub File Size:||17.25 Mb|
|Price:||Free* [*Free Regsitration Required]|
ISO part 4 section 5 APDU level data structures
The logical organization of ifletype in a card consists of following structural hierachy of dedicated files:. 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: The path allows an unambiguous selection af any file from the MF or from the current DF.
The security attributes of file depend on: Within each EF of cyclic structure, the record numbers shall be sequentially assigned in the opposite order, i. Easy chip card integration with our smart card. The tag field T consists of one or more consecutive bytes. Secure messaging is achieved by applying one or more security mechanisms.
The DF at the root is called the master file MF. The following additional rule is defined for linear structures and for cyclic structures: The file reference denotes the file where the kso reference is valid.
F I G U R E 2
The maximum number of bytes expected in the data field of the response APDU is denoted by Le length of expected data. In this case, the card computes a string of concealing bytes and adds it by exclusive-or to data bytes received from or sent to the outside world.
In order to select unambiguously by DF name e. Referencing by file identifier — Any file may be referenced by a file identifier coded on 2 bytes. Therefore the first created record is in the first logical position.
By the relevant security mechanisms, 77816 the selected security items, the card shall produce all the requested security mechanism data objects. This mechanism may be used to provide a confidentiality service, e.
The present specifications of the padding rules do not preclude such a feature. Within an EF of record structure, data unit referencing may not provide the intended result because the storage order of the records in the EF is not known, e. Referencing by record number shall not affect the record pointer. Each data object as defined in 1. The subsequent clauses specify coding conventions for the class byte, the instruction byte, the parameter bytes, the data field bytes and the status byte.
This clause defines 3 types of SM-related data objects: Concealment thus requires no padding and the data objects concealed in the value field are recovered by the same operation.
Consequently, the body consists of the Lc field followed by the data field. This page was last edited on 19 Aprilat When a file cannot be implicitly selected, it shall be possible to select it by at least one of the following methods:. 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.
Data referencing method, record numbering method and data unit size are EF-dependent features. According to its abstract, it specifies interindustry commands for integrated circuit cards either with contacts or without contacts that may be used for cryptographic operations. It may be maintained, recovered or lost by file selection see 6. Therefore the first record record number one, 1 is the first ic record. Transparent structure — The EF is seen at the interface as a sequence of data units.
The use of a block cipher may involve padding. The first byte of the value field is named the type cryptogram descriptor byte and is mandatory. If no file reference is present, then the key reference is valid in the current DF. 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 linear structure, the record numbers shall be sequentially assigned when writing or appending, i. The first output results from the first input. Personal verification through biometric methods”. Each non TLV-coded data field shall consist of one or more data elements, according to the specifications of the respective command. A logical channel, as seen at the interface, works as a logical fiketype to a DF.
SM data objects incorrect. Identification of persons using biometric methods is outside the scope of this standard. 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 following additional rules are defined for linear structures and for cyclic structures: For each command, an appropriate clause provides more detailed meanings.