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):||4 August 2004|
|PDF File Size:||5.94 Mb|
|ePub File Size:||6.13 Mb|
|Price:||Free* [*Free Regsitration Required]|
Data referencing method, record numbering method and data unit size are EF-dependent features. 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.
Consequently, the body consists of the Lc field followed by the data field. Within an EF of record structure, data unit referencing may not jso the intended result because the storage order of the records in the EF is not known, e.
When numbered, its number is 0. Cyclic EF with records of fixed filtype. In case 3, the length Lc is not null; therefore the Lc field is present and the data field consists of the Lc subsequent bytes. Personal verification through biometric methods”. No byte is used for Lc valued to 0 No data byte is present.
According to its abstract, it specifies the Data Elements DEs used for interindustry interchange based on integrated circuit cards ICCs both with contacts and without contacts. 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:.
This page was last edited on 19 Aprilat 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.
Each command message may carry a response descriptor template fixing the data objects required in response. Alternately, using secret internal data, the card computes a data element cryptographic checksum or digital signature and inserts it in the data sent to the outside world.
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. ISO standards by standard number. The security attributes of file depend on:.
ISO part 4 section 5 APDU level data structures
The subsequent clauses specify coding conventions for the class byte, the instruction byte, the parameter bytes, the data field bytes and the status byte. Within an EF of record structure, records may have oso same record identifier, in which case data contained in the records may be used for discriminating between them. However, logical channels may share application-dependent security status and therefore may have security-related command interdependencies across logical channels e.
Cards with contacts — Physical characteristics”. Filftype by record number shall not affect the record pointer. Data objects for confidentiality are intended for carrying a cryptogram which plain value consists of one of the following 3 cases:. If no file reference is present, then the key reference is valid in the current DF. Created inupdated inamended in NOTES An EF of record structure may support data unit referencing and in case it does, data units may contain structural information along with data, e.
ISO/IEC – Wikipedia
The current input is the exclusive-or of the previous output with the current data block. The following structures of EFs are defined: Retrieved 19 April Concealment thus requires no padding and the data objects concealed in the value field are recovered by the same operation.
Data is considered to be stored in a single continuous sequence of records within an EF of record structure or of data units within an EF of transparent structure. It gives the identifier, name, description, format, coding and layout of each DE and defines the means of retrieval of DEs from the card. For example, the last possible position of a template ffiletype cryptographic checksum is just before the first data object integrated in the computation.
Command-response pairs work as currently described. Figure 1 illustrates an example of the logical file organization in a card.
F I G U R E 2
The file reference denotes the file where 78816 key reference is valid. If a card supports the logical channel mechanism, then the maximum number of available logical channels is indicated in the card capabilities see 8. This clause defines 3 types of SM-related data objects: The security attributes, when they exist, define the allowed actions and the procedures to be performed to complete such actions.
Transparent structure — The EF is seen at the interface as a sequence of data units.
The basic logical channel shall not be closed. Identification of persons using biometric methods is outside the scope of this standard. Linear EF with record of fixed size. The first input is the exclusive-or of the initial check block with the first data block.