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 [4].
| Author: | JoJozilkree Mezinos |
| Country: | South Africa |
| Language: | English (Spanish) |
| Genre: | Technology |
| Published (Last): | 14 October 2009 |
| Pages: | 129 |
| PDF File Size: | 17.26 Mb |
| ePub File Size: | 12.37 Mb |
| ISBN: | 671-3-72028-533-6 |
| Downloads: | 73641 |
| Price: | Free* [*Free Regsitration Required] |
| Uploader: | Gardagor |
ISO standards by standard number. The length field consists of 1 or 3 consecutive bytes. The use of a block cipher may involve padding. According to its abstract, it specifies interindustry commands for integrated circuit cards both with contacts and without contacts for card and file management, e.
Data objects of the other classes may be present e. It may be maintained, recovered or lost by file selection see 6. For example, a command may fix control references for the next iev.
The last possible position of a control reference template is just before the first data object to which the referred mechanism fiiletype. Command-response pairs work as currently described. 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.
Consequently, the body consists of the Le field.
If the response descriptor provides auxiliary data, then the respective data object shall be empty in the response. Annexes are provided that give examples of operations related to digital signatures, certificates and the import and export of asymmetric keys. For cards indicating the extension of Lc and Le see 8.
Created inamended in,updated in When there is no current record, the next occurrence shall be equivalent to the first occurrence. The current output results from the current input.
ISO part 4 section 5 APDU level data structures
Data may be flletype as records, as data units or as data objects. The tag field T consists of one or more consecutive bytes.
These commands cover the entire life cycle of the card and therefore some commands may be used before the card has been issued to the cardholder or after the card has expired. Referencing by record number shall not affect the record pointer.
Easy chip card integration with our smart card. The ixo output results from the first data block.
ISO/IEC – Wikipedia
Reference to a record or to a data unit outside an EF is an error. The present specifications of the viletype rules do not preclude such a feature. NET library for chip cards. A step in an application protocol consists of sending a command, processing it in the receiving entity and sending back the response.
The result of an authentication may be logged in an internal EF according to the requirements of the application. Concealment thus requires no padding and the data objects concealed in the value field are recovered by the same operation.
The following two types of EFs are defined: The length Le is also null; therefore the Le field is empty. The length of Le is not null; therefore the Le field is present.
The logical organization of data in a card consists of following structural hierachy of dedicated files:. The length Le is null; therefore the Le field is empty.
Consequently, the body consists of the Lc field followed by the data field and the Le field.
Those data objects shall integrate data block by data block in the current check block. Record structure — The EF is seen at the interface as a fuletype of individually identifiable records.
A logical channel, as seen at the interface, works as a logical link to a DF. This mechanism may be giletype for protecting the rights of a provider.
ISO/IEC 7816
The loaded data may contain, for example, code, keys and applets. When padding is applied but not indicated the rules defined in 1. Commands for application management in a multi-application environment”.
Commands for card management”. This clause contains information on the logical structure of data as seen at the interface, when processing interindustry commands for interchange.
In the absence of an algorithm reference and when no mechanism is implicitly selected for confidentiality a default mechanism shall apply. The data fields of some commands e. 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.