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):||2 May 2006|
|PDF File Size:||15.60 Mb|
|ePub File Size:||1.58 Mb|
|Price:||Free* [*Free Regsitration Required]|
77816-5 inupdated in If no initial data reference is present and no initial check block is implicitly selected, then the null block shall be used. 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. Created inupdated inamended inupdated in Registration of application providers Status: 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.
Organization, security and commands for interchange”. If the auxiliary data is less than k bytes, then it is headed by bits set to 0, up to the block length. Concealment thus requires no padding and the data objects 77816-5 in the value field are recovered by the same operation. Transparent structure — The EF is seen at the interface as a sequence of data units. That is, command interdependencies on one logical channel shall be independent of command interdependencies on another logical channel.
ISO/IEC – Wikipedia
If present, the data objects of the other classes shall be integrated in such a computation. Within each EF of transparent structure, each data unit can be referenced by an offset e. 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.
This mechanism may be used for protecting the right of the user. Cyclic EF with records of fixed size. Your basket is empty.
Annexes are 781-5 that give examples of operations related to digital signatures, certificates and the import and export of asymmetric keys. The use of a block cipher may involve padding.
ISO part 4 section 5 APDU level data structures
This mechanism may be used for protecting privacy and for reducing the possibilities of message filtering. Therefore the first record record number one, 1 is the first created record. Such a command APDU carries no length 78166-5.
716-5, the body consists of the Lc field followed by the data field. By the relevant security mechanisms, with the selected security items, the card shall produce all the requested security mechanism data objects. The goal of secure messaging SM is to protect [part of] the messages to and from a card by ensuring two basic security functions: The transmission and reception of data fields may be interleaved with the execution of security mechanisms.
Learn more about the cookies we use and how to change your settings. The current input is the exclusive-or of the previous output with the current data block.
F I G U R E 2
In order to select unambiguously any file by its identifier, all EFs and DFs immediately under a given DF shall have different file identifiers. The subsequent clauses specify coding conventions for the class byte, the instruction byte, the parameter bytes, the data field bytes and the status byte. Each data field shall have one of the following three structures. The first byte of the value field is named the type cryptogram descriptor byte and is mandatory.
The following additional rule is defined for linear structures and for cyclic structures: This clause contains information on the logical structure of data as seen at the interface, when processing interindustry commands for interchange. Data objects for confidentiality are intended for carrying a cryptogram which plain value consists of one of the following 3 cases:.