Identification cards - Integrated circuit(s) cards with contacts - Part 6: Interindustry data elements (ISO/IEC 7816-6:1996)

Migrated from Progress Sheet (TC Comment) (2000-07-10): Awaiting pulished ISO standard. ++ Accurate dates to be supplied by TC 224.

Identifikationskarten mit integrierten Schaltkreisen und Kontakten - Teil 6: Interindustrielle Datenelemente (ISO/IEC 7816-6:1996)

Cartes d'identification - Cartes à circuit(s) intégré(s) avec contacts - Partie 6: Eléments de données interindustrielles (ISO/IEC 7816-6:1996)

Identification cards - Integrated circuit(s) cards with contacts - Part 6: Interindustry data elements (ISO/IEC 7816-6:1996)

General Information

Status
Withdrawn
Publication Date
17-Jun-1997
Withdrawal Date
11-Jan-2000
Current Stage
9960 - Withdrawal effective - Withdrawal
Start Date
12-Jan-2000
Completion Date
12-Jan-2000

Buy Standard

Standard
EN ISO/IEC 7816-6:1998
English language
20 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Identification cards - Integrated circuit(s) cards with contacts - Part 6: Interindustry data elements (ISO/IEC 7816-6:1996)Identifikationskarten mit integrierten Schaltkreisen und Kontakten - Teil 6: Interindustrielle Datenelemente (ISO/IEC 7816-6:1996)Cartes d'identification - Cartes a circuit(s) intégré(s) avec contacts - Partie 6: Eléments de données interindustrielles (ISO/IEC 7816-6:1996)Identification cards - Integrated circuit(s) cards with contacts - Part 6: Interindustry data elements (ISO/IEC 7816-6:1996)35.240.15Identifikacijske kartice in sorodne napraveIdentification cards and related devicesICS:Ta slovenski standard je istoveten z:EN ISO/IEC 7816-6:1997SIST EN ISO/IEC 7816-6:1998en01-junij-1998SIST EN ISO/IEC 7816-6:1998SLOVENSKI
STANDARD



SIST EN ISO/IEC 7816-6:1998



SIST EN ISO/IEC 7816-6:1998



SIST EN ISO/IEC 7816-6:1998



SIST EN ISO/IEC 7816-6:1998



ISO/lEC 7816-6: 1996 (E) Contents Page Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv Scope . 1 Normative references . 1 Definitions, abbreviations and notations . 1 3.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 1 3.2 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3.3 Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 2 4 Identification of data elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4.1 Principles . 2 4.2 Data object structure . 3 4.3 Indirect DE referencing . 3 4.4 Tag allocation schemes . 4 5 Retrieval of data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .‘. 5 5.1 5.2 5.3 5.4 5.5 5.6 Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Retrieval of DOS after ATR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Retrieval of data in files . . . . . . . . .*. 5 Retrieval of data in FCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Retrieval of data using the GET DATA command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Indirect retrieval of DES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 5 0 ISO/IEC 1996 All rights resewed. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the publisher. ISO/IEC Copyright Office l Case postale 56 l CH-1211 l Gen&e 20 l Switzerland Printed in Switzerland SIST EN ISO/IEC 7816-6:1998



0 ISO/IEC lSO/lEC 7816-6: 1996 (E) 6 Coding of specific DES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 ID0 5B Name (of an individual) . 5 ID0 6B Qualified name . 6 ID0 6A Log-in template . 6 ID0 5F2F Coding of the PIN usage policy . 7 ID0 6C Cardholder images . 7 ID0 6D Application image template . 7 Magnetic stripe data . 7 ID0 7F20 Display control . 7 Interchange profile . 7 7 Maintenance of the IDOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 8 7.1 IDOs from other parts of lSO/IEC 7816 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.2 IDOs from other standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8 List of interindustry data objects .,. 9 8.1 Data objects in alphabetic order . 9 8.2 Data objects in numeric order . 12 Annexes A Interindustry templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 B Examples of coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 . . . III SIST EN ISO/IEC 7816-6:1998



lSO/lEC 7816-6: 1996 (E) 0 ISO/IEC Foreword IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of IS0 or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. IS0 and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the work. In the field of information technology, IS0 and IEC have established a joint technical committee, ISO/IEC JTCI. Draft International Standards adopted by the joint technical committee are circulated to the national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. International Standard ISO/IEC 7816-6 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 17, Identification cards and related devices. ISO/IEC 7816 consists of the following parts, under the general title identification cards - integrated circuit(s) cards with contacts: - Part I : Physical characteristics - Part 2 : Dimensions and location of the contacts - Parf 3: Electronic signals and transmission protocols - Part 4: Interindustry commands for interchange - Parf 5: Numbering system and registration procedure for application identifiers - Part 6: Interindustry data elements Annex A forms an integral part of this part of ISO/IEC 7816. Annex B is for information only. SIST EN ISO/IEC 7816-6:1998



INTERNATIONAL STANDARD 0 ISO/IEC lSO/lEC 7816-6:1996 (E) Identification cards - Integrated circuit(s) cards with contacts - Part 6: Interindustry data elements 1 Scope This part of ISO/IEC 7816 specifies directly or by reference the Data Elements (DE), including composite DES, used in interindustry interchange, based on integrated circuit cards (ICCs). It identifies the following characteristics of each DE: - Identifier - Name - Description and IS0 reference - Format and coding (if not available in other IS0 standards or parts of ISO/IEC 7816). The layout of each DE is described as seen at the interface between the interface device (IFD) and the ICC. This part of ISO/IEC 7816 defines the means of retrieval of the DES in the card (historical bytes, reset, command(s) to perform and commands defined in this international standard). This part of ISO/IEC 7816 provides the definition of DES without consideration of any restrictions on the usage of the DES. It is intended that new interindustry data objects be incorporated into this standard; see clause 7 for the procedure to be followed. 2 Normative references The following standards contain provisions which, through reference in this text, constitute provisions of this part of ISO/IEC 7816. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this part of lSO/IEC 7816 are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Members of the IEC and IS0 maintain registers of currently valid International Standards. IS0 639: 1988, Code for the representation of names of languages. ISO/IEC 646: 1991, Information technology - IS0 7-bit coded character set for information interchange. IS0 3166: 1993, Codes for the representation of names of countries. ‘) To be published. IS0 4217: 1995, Codes for the representation of currencies and funds. IS0 4909: 1987, Bank cards - Magnetic stripe data content for track 3. ISOIIEC 7501-I : 1993, Identification cards - Machine readable travel documents - Part I: Machine readable passport. ISO/IEC 7813: 1995, Identification cards - Financial transaction cards. I SO/I EC 78 16-4: 1995, Information technology - Identification cards - Integrated circuit(s) cards with contacts - Part 4: Interindustry commands for interchange. ISOIIEC 7816-5: 1994, Identification cards - Integrated circuit(s) cards with contacts - Part 5: Numbering system and registration procedure for application identifiers. IS0 8583: 1993, Financial transaction card originated messages - Interchange message specifications. ISOII EC 8825-l : 1995, Information technology - ASN. I encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). ISOII EC 8859-l : 1987, Information processing - 8-bit single-byte coded graphic character sets - Part I: Latin alphabet No. 1. IS0 9992=2:---J, Financial transaction cards - Messages between the Integrated Circuit Card and the Card Accepting Device - Part 2: Functions, messages (commands and responses), data elements and structures. ISOII EC 10918-I : 1994, Information technology - Digital compression and coding of continuous-tone still images: Requirements and guidelines. ISOIIEC 11544: 1993, Information technology - Coded representation of picture and audio information - Progressive bi-level image compression. 3 Definitions, abbreviations and notations 3.1 Definitions For the purposes of this part of ISO/IEC 7816, the following definitions apply. 1 SIST EN ISO/IEC 7816-6:1998



lSO/lEC 7816-6: 1996 (E) 0 ISO/IEC 3.1 .l composite data element: a data element made up of a concatenation of zero, one or more data element(s). 3.1.2 data element: as defined in ISO/IEC 7816-4. 3.1.3 data object: as defined in ISO/IEC 7816-4. 3.1.4 element list: DES. 3.1.5 headerlist: a without delimiters. 3.1.6 interindustry data element: data element for items of information concerning concatenation of tag/length pairs use in interindustry interchange. 3.1.7 interindustry data object: data object for use in interindustry interchange. 3.1.8 taglist: a concatenation of tag/length pairs without delimiters. 3.1.9 template: value field of a constructed data object, defined to give a logical grouping of data objects. 3.2 Abbreviations For the purposes of this part of ISO/IEC 7816, the following abbreviations apply. ASN.l ATR DE DF DO EF FCI ICC IDE ID0 LRC PIN Abstract syntax notation one Answer-to-reset Data element Dedicated file Data object Elementary file File control information Integrated circuit card Interindustry data element Interindustry data object Longitudinal redundancy check Personal identification number 3.3 Notations a n alphabetic character numeric, coded in binary coded decimal format Any number following the notations denotes the number of digits or characters. For example: a3 means 3 alphabetic characters n.3 means up to 3 binary coded decimal digits n2.4 means 2, 3 or 4 binary coded decimal digits 4 Identification of Data Elements 4.1 Principles The following principles apply to the identification of DES: 4.1.1 For the purposes of this part of ISO/IEC 7816 a data element is generally presented in the value field of a data object. 4.1.2 For the purposes of this part of ISO/IEC 7816 a data object is a concatenation of the following string of bytes: - a mandatory tag field, referred to as a tag; - a mandatory length field indicating a length L; - a conditional value field of L bytes (when L is not equal to ‘00’). 4.1.3 For purposes of retrieval and referencing in interchange: - a DE shall be associated with the tag of a DO; - the DE may be encapsulated in this DO. 4.1.4 The context according to which a DO is identified depends: - either on the nesting of the DO in a template or; - on the application currently selected. 4.1.5 When no application is selected all DOS shall be interpreted according to ISO/IEC 7816. 4.1.6 A DE may be referenced directly by its associated tag. It may be associated with another DE which indicates the context to which it belongs. 4.1.7 A DE may be referenced indirectly by one or more command to perform DOS. 4.1.8 The DOS are described as seen at the interface between the ICC and the interface device. 4.1.9 Within ISO/IEC 7816 a tag denotes a type of DE. 4.1 .lO There may be multiple occurrences of the same ID0 in a card. S special character an alphanumeric character ans alphanumeric and special characters . . . between 2 numbers denotes a range of values. 2 SIST EN ISO/IEC 7816-6:1998



0 ISO/IEC lSO/lEC 7816-6: 1996 (E) The coding of the second byte, when present, is: 4.2 Data object structure The following DO structures are supported: - primitive DO ITILIVI where T = Tag, L = Length, V = Value - constructed DO 1 TI LI TI 1 LI 1 VI 1 . . . 1 T,, 1 L, 1 V, 1 T = tag of constructed DO L = length of the string (template) Tl to V, TI.” = tag of a DRn l-l.” = length of VI.” VI.” = value of a DO,.” 4.2.3 Structure of the tag The tag consists of one or two bytes. The coding of these bytes shall be consistent with the basic encoding rules of ASN.1. Table 1 defines the first byte. Table 1 - Structure of the first byte of the tag b8 b7 b6 b5 b4 b3 b2 bl Meaning 0 0 - - - - - - Not defined in this part of ISO/IEC 7816 0 1 - - - - - - Defined in this part of ISO/IEC 7816. Application class, unambiguous identification 1 0 - - - - - - Defined in this part of ISO/IEC 78l-6 and only to be used within a template - see note below 1 1 - - - - - - Not defined in this part of ISO/IEC 7816. Reserved for private use - 0 - - - - - Primitive DO 0 1 - - - - - . Constructed DO . I- -1-l’ ’ ’ ’ ’ / g;;;e / 0 0 - x x x x x Tag number - range 0.30 Not all equal to 1 NOTE - Context dependent class tags (b8b7=10) are used out of templates for the file control information and secure messaging, see ISO/lEC 7816-4. b8 =0 b7 to bl = binary value of the tag number in the range 31 .I27 4.2.2 Structure of the length All lengths are expressed in bytes. The length consists of one or more bytes. The coding of these bytes shall be consistent with the basic encoding rules of ASN.l and shall be as defined in table 2. Table 2 - Coding of the length value Range # of 1st byte 2nd byte 3rd byte bytes 0.127 1 binary value none none 0.255 2 '81' binary none value 0.65,535 3 '82' binary value ms byte Is byte ms = most significant; Is = least significant 4.2.3 Format of the value The format of the value depends on the type of the DE. When the length of the DE is not expressed as a number of bytes, the mapping onto a byte string should be defined in the context of the respective DE (see clause 8). If not specified otherwise, the appropriate number of least significant bits of the last byte shall be set to 1. 4.3 Indirect DE referencing The following IDOs are used: - the wrapper, tag '63', constructed as described in 5.6; - the DO taglist, tag ‘5C’, the value of which is a (concatenation of) tag(s) without delimiter; - the DO headerlist, tag ‘5D’, the value of which is a concatenation of tag/lengths without delimiter; - the element list, tag ‘5F41', only to be used within the wrapper, tag ‘63’; - the Command to Perform, tag '52', used as defined in ISO/IEC 7816-4; - the path, tag ‘51', used as defined in ISO/IEC 7816-4. 3 SIST EN ISO/IEC 7816-6:1998



ISO/IEC 7816-6: 1996 (E) 0 ISO/IEC 4.4 Tag allocation schemes ISO/IEC 78 16-6 allocates some ASN.l -BER application class tags (context independent) as indicated in table 1. The default tag allocation scheme for IDOs in an ICC is defined in this part of ISO/IEC 7816 (see table 8). 4.4.1 Compatible tag allocation schemes These tag allocation schemes use IDOs as defined in ISO/IEC 7816, and further DOS which - either shall use context-dependent class tags (starting with 8 ,9, A, B) within templates defined in this part of ISO/IEC 7816 (templates ‘65, ‘66’, ‘67’, v 9 . W 9 - or shall be nested within templates with tags in the range ‘70’ to ‘77’. Within these templates the meaning of application class tags is not defined in ISO/IEC 7816 except for the tags defined in table 4. In order to identify a compatible tag allocation scheme and the authority responsible for the scheme, a Tag Allocation Authority DO with a tag of ‘78’ (defined in 4.4.4) may be used. If the tag allocation authority is only valid for data within a DF, then the FCI of the DF may contain the Tag Allocation Authority DO. If the tag allocation authority is valid for the entire card then the DO may be present in the initial data string of the ATR file (as defined in ISO/IEC 7816-4). An ID0 listed in 4.4.4 may be included in the templates ‘70’ to ‘77’ indicating the authority responsible for the allocation of tags used in that template. NOTE - the use of these schemes is either implicit (use of context dependent tags) or explicit (presence of the ID0 with tag ‘78’). 4.4.2 Coexistent tag allocation schemes For these tag allocation schemes, DOS may use tags with another interpretation than ISO/IEC 7816. In order to identify a coexistent tag allocation scheme, a Tag Allocation Authority DO with a tag of ‘79’ (defined in 4.4.4) identifying the authority responsible for the scheme shall be used. If the tag aflocation authority is only valid for data within a DF then the FCI of the DF shall contain the Tag Allocation Authority DO. If the tag allocation authority is valid for the entire card then the DO shall be present in the initial data string of the ATR file (as defined in ISO/IEC 7816-4). All IDOs shall be nested within templates, tag ‘7E’. In such a scheme tags ‘79’ and ‘7E’ shall not be given another interpretation. 4 Besides ‘79’ and ‘7E’ the tags in table 3, defined in ISO/IEC 7816, shall not be reallocated by a coexistent tag allocation scheme: Table 3 - Tags reserved for ISOllEC , Tag ID0 62 denotes file control parameters (FCP) template, as defined in ISO/IEC 7816-4 64 denotes file management data (FMD) template, as defined in ISO/IEC 7816-4 6F denotes FCI template. as defined in ISO/IEC 7816-4 I I 70 resewed for secure messaging template of ISO/IEC 7816 4.4.3 Independent tag allocation schemes For these tag allocation schemes DOS may use tags with another interpretation than ISO/IEC 7816, but which do not comply with 4.4.2. Such tag allocation schemes do not allow interindustry interchange and are not in compliance with ISO/IEC 7816-6. A consistent use of the IDOs discretionary data, tag ‘53’ and discretionary DOS, tag ‘73’, allows the use of proprietary objects whilst remaining compliant to ISO/IEC 7816-6. 4.4.4 Tag allocation authority Within templates ‘78’ or ‘79’ the IDOs shown in table 4 indicate which authority is responsible for tag allocation: Table 4 - Taas for allocation of authorities Tag 06 41 42 4F object identifier, as defined in ISO/IEC 8825, see example of codina in Annex B defined in ISO/IEC 7816-4 and used to indicate at least a country defined in ISO/IEC 7816-4 and used to indicate an issuer indicates an Application Identifier (AID), as defined in ISO/IEC 7816-5. SIST EN ISO/IEC 7816-6:1998



0 ISO/IEC ISO/lEC 7816-6: 1996 (E) 5 Retrieval of data 5.6 Indirect retrieval of DES This clause defines standard retrieval procedures of DES. 5.1 Principles Before selecting an application, IDOs should be retrieved directly or indirectly from : - the historical bytes; the initial data string; - the ATR file; - the Directory file (DIR file) in the above order, when present. These IDOs shall be interpreted according to clause 4. Once an application is selected, IDOs should be retrieved directly or indirectly from: - the FCI of the DF; - other specific Elementary Files (EFs) within the current DF. In this case these IDOs may also be retrieved by use of GET DATA command(s). For indirect referencing the wrapper DO is used. The wrapper DO has the tag ‘63’, is constructed and shall consist of two parts: the first part contains either - the ID0 taglist, tag ‘5C’, denoting that the DES to be retrieved are presented as DOS or; - the ID0 headerlist, tag ‘5D’, denoting that the DES to be retrieved are presented as a string of values, in the same order as in the taglist; - the ID0 element list, tag ‘5F41’, denoting that the elements to be retrieved are not presented as DOS, but under application control. The structure of the element list as well as the information returned are outside the scope of ISO/IEC 7816. the second part contains - a path to an EF, tag ‘51’; - and/or one (or more) ‘command to perform’ DOS, tag ‘52’, as defined in ISO/IEC 7816-5. The following diagram is an example of a wrapper containing a taglist and one ‘command to perform’: 1 63 I L 1 5C I L ITagl, Tag2, Tag3.1 52 I L 1 CTP 1 5.2 Retrieval of DOS after ATR If indicated in the Historical Bytes, DOS may be retrieved after reset and possible Protocol Type Selection (PTS) by the use of the initial access data, according to lSO/lEC 7816-4. Only one indirect reference shall be given in a wrapper. There may be more than one wrapper. All these DOS shall have tags complying with 4.4. A DO referenced according to ISO/IEC 7816 in the tag list, or a DE referenced another way in the DE list, shall be either 5.3 Retrieval of data in files DOS may be retrieved in reserved files (DIR file and ATR file). This may be indicated in the historical bytes. Selection and reading of these files is defined in ISO/IEC 7816-4. The content of the DIR file is defined in ISO/IEC 7816-5. Information on the content of the ATR file is given in ISO/IEC 7816-4. All these DOS shall have tags defined by ISO/IEC 7816. DES may be retrieved in other files denoted by their path in a wrapper DE (see 5.6). Selection and reading of an EF known by its path is defined in ISO/IEC 7816- 4. 5.4 Retrieval of data in FCI Data may be present in the FCI according to ISO/lEC 7816-4. contained in a file denoted by its path, see 5.3 for the retrieval or - be (part of) the response to the last ‘command to perform’ indicated in the wrapper. The commands shall be executed in the order presented. 6 Coding of specific DES 6.1 ID0 5B Name (of an individual) A composite DE of variable length up to 39 characters, made up of: - Surname (family name); - Given name(s) (forename(s)); 5.5 Retrieval of data using the GET DATA command DOS may be retrieved by use of the GET DATA command as defined in ISO/IEC 7816-4. - Name suffix (e.g. Jr, number.); - Filler(s) as defined and used in ISO/IEC 7501-l. They shall be coded according to ISO/IEC 8859-l. 5 SIST EN ISO/IEC 7816-6:1998



ISO/IEC 7816-6: 1996 (E) 0 ISO/IEC National languages with non-Latin characters shall be transliterated or transcribed into the Latin alphabet using the appropriate IS0 standard. In cases where: - names cannot be shown in full; - or a special alphabet is needed; - or the transliteration or transcription is not sufficient the ID0 “qualified name” should be used. 6.2 ID0 6B Qualified name A constructed DO of variable length, made up of: - one or several object identifiers, tag ‘06’, referring to the standards defining the presentation of the qualified name; - a name tag ‘80’ (primitive) or ‘AO’ (constructed), the value and coding of which is defined by the aforementioned standards; - other related optional information, (e.g. sex, nationality, place of birth). 6.3 ID0 6A Log-in template A log-in template is a constructed object of variable length. The value shall consist of one or more primitive objects such as qualifiers, numbers, text and times, as specified hereafter. 6.3.1 Qualifier The tag shall be ‘80’. The value (1 to 9 bytes) shall consist of a mandatory first byte coding a rank followed by, at most, 8 optional bytes coding a mnemonic. This shall qualify the subsequent objects in a template, until the next qualifier, if any. The rank is an integer valued from 0 to 255. If two or more qualifiers have the same rank within the same context, then only the set of objects qualified by the most recent one is valid. The mnemonic is a string of 7-bit characters (b8 set to 0, see ISO/IEC 646) to be displayed at the man- machine interface. 6.3.2 Number The tag shall be ‘81’. The value of the variable length shall consist of an even number of nibbles where each nibble codes one character for representing a telephone number, according to table 5. Table 5 - Nibble decoding Nibble Character Meaning ‘0’ to ‘9’ 0 to 9 Decimal digits ‘A’ ( Opening bracket ‘Is’ ) Closing bracket ‘C’ c Requirement for connecting to the line before continuing ‘D’ + Introduction of an international telephone number ‘E’ If first, introduction of a number to be used with
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.