ANSI INCITS ISO IEC 7816-6-1996 Identification cards - Integrated circuit(s) cards with contacts - Part 6 Interindustry data elements (Adopted by INCITS).pdf

《ANSI INCITS ISO IEC 7816-6-1996 Identification cards - Integrated circuit(s) cards with contacts - Part 6 Interindustry data elements (Adopted by INCITS).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS ISO IEC 7816-6-1996 Identification cards - Integrated circuit(s) cards with contacts - Part 6 Interindustry data elements (Adopted by INCITS).pdf（21页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL STANDARD ISO/IEC 7816-6 First edition 1996-05-I 5 Identification cards - Integrated circuit(s) cards with contacts - Part 6: Interindustry data elements Cartes didentification - Cartes B circuit(s) inthgrk(s) avec contacts - Partie 6: hments de don see clause 7 for the procedure to be

2、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

3、 on this part of ISO/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 language

4、s. 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

5、 stripe data content for track 3. ISO/IEC 7501-l: 1993, identification cards - Machine readable travel documents - Part 1: Machine readable passport. ISO/IEC 7813: 1995, identification cards - Financial transaction cards. ISO/IEC 7816-4: 1995, information technology - Identification cards - Integrat

6、ed circuit(s) cards with contacts - Part 4: Interindustry commands for interchange. ISO/IEC 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 ori

7、ginated messages - Interchange message specifications. ISO/IEC 8825-l : 1995, Information technology - ASN. 1 encodjng rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). ISO/IEC 8859-l: 1987, information processing - - a mandato

8、ry 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

9、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

10、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 Ther

11、e may be multiple occurrences of the same ID0 in a card. 0 ISO/IEC ISO/iEC 7816-6: 1996 (E) 4.2 Data object structure The following DO structures are supported: - primitive DO py7-p-j where T = Tag, L = Length, V = Value - constructed DO 1 Tj LI TI LI 1 VI 1 . . . 1 T, 1 Ln 1 Vn 1 T = tag of constru

12、cted DO L = length of the string (template) T1 to Vn Ti . n = tag of a DOI. Ll.“ = length of VI., Vi.” = value of a DOI., 4.2.1 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.l. Table 1 defines the first b

13、yte. Tab b8 b7 0 0 0 1 1 0 1 1 itructure of the first b b5 b4 b3 b2 bl - - - - _ _ _ _ _ _ - - - - - 1 1 1 1 1 x x x x x e of the tag Meaning Not defined in this Dart of ISOllEC 7816 Defined in this Dart of ISO/IEC 7816. Application class, unambiguous identification Defined in this part of ISOllEC 7

14、816 and only to be used within a template - see note below Not defined in this part of ISO/IEC 7816. Reserved for private use Primitive DO Constructed DO Tag number contained in the next byte - range 31127 Tag number - range 030 Not all equal to 1 NOTE - Context dependent class tags (b8b7=10) are us

15、ed out of templates for the file control information and secure messaging, see ISO/IEC 7816-4. The coding of the second byte, when present, is: b8 =0 b7 to bl = binary value of the tag number in the range 31127 4.2.2 Structure of the length All lengths are expressed in bytes. The length consists of

16、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. 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

17、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 use

18、d: - 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

19、 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 ISOllEC 7818-8: 1998 (E) 0 ISO/IEC 4.4 Tag allocation schemes ISO/IEC 7816-6 allocates some ASN.l -BER application class tags (context independen

20、t) 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

21、 class tags (starting with 8 ,9, A, B) within templates defined in this part of ISO/IEC 7816 (templates 65, 66, 67, 6E); - 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 t

22、ags 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

23、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 respon

24、sible 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 interpreta

25、tion 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 allocation authority is only valid for data within a DF then the FCI of th

26、e 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

27、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 resewed for ISOllEC Tag ID0 62 denotes file control parameters (FCP) template, as defined in ISO/IEC 7816-4 64 d

28、enotes file management data (FMD) template, as defined in ISO/IEC 7816-4 6F denotes FCI template, as defined in ISO/IEC 7816-4 7D reserved 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 interpretat

29、ion 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 wh

30、ilst 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 - Tags for allocation of authorities Tag ID0 06 object identifier, as defined in ISO/IEC 8825, see exampl

31、e of coding in Annex B 41 defined in ISO/IEC 7816-4 and used to indicate at least a country 42 defined in ISO/IEC 7816-4 and used to indicate an issuer 4F indicates an Application Identifier (AID), as defined in ISO/IEC 7816-5. 0 ISO/IEC lSO/lEC 7818-6: 1996 (E) 5 Retrieval of data This clause defin

32、es 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 int

33、erpreted 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). 5.2 Retrieval of DOS

34、 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 ISO/IEC 7816-4. All these DOS shall have tags complying with 4.4. 5.3 Retrieval of data in files DOS may be retrieved in re

35、served 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

36、 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/IEC 7816-4. 5.5 Retrie

37、val 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. 5.6 Indirect retrieval of DES 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 contain

38、s 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 element

39、s 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 define

40、d 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 Only one indirect reference shall be given in a wrapper. There may be more than one wrapper. A DO referenced according to ISO/IE

41、C 7816 in the tag list, or a DE referenced another way in the DE list, shall be either - 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

42、 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); - Name suffix (e.g. Jr, number.); - Filler(s) as defined and used in ISO/IEC 7501-l. They shall be coded according to I

43、SO/IEC 8859-l. 5 ISOllEC 7818-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 translitera

44、tion 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 (primit

45、ive) 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 o

46、r 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 subsequen

47、t 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 t

48、o 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. Nibble 0 to 9 A B C D E

49、F L Table 5 - Nibble decodina Character 0 to 9 + Meaning Decimal digits Opening bracket Closing bracket Requirement for connecting to the line before continuing Introduction of an international telephone number If first, introduction of a number to be used without prefix; if not first, requirement for a delay (2 seconds) before continuing Reserved for padding 6.3.3 Text The tag shall be 82. The value of the variable length shall consist of one or more bytes where each byte codes one charac