ANSI ISO IEC 7816-5-1994 Identification cards - Integrated circuit(s) cards with contacts - Part 5 Numbering system and registration procedure for application identifiers《信息技术.识别卡..pdf

1、INTERNATIONAL STANDARD ISOJIEC 7816-5 First edition 1994-06-l 5 Identification cards - Integrated circuit(s) cards with contacts - Part 5: Numbering system and registration procedure for application identifiers Cartes didentification - Cartes 9 circuit(s) inthgrt$(s) B contacts - Partie 5: Systhme d

2、e numhotation et proc - The application label; - The path to a file; - A command to perform; - Discretionary data; - The application template. 5 Coding of the data elements 5.1 Structure of an ASN.l object If a data element defined in this clause is represented as an ASN.l object, it shall be encode

3、d according to table 1 Table 1 - ASN.l coding of data elements TAG LENGTH(L) VALUE(data element) TYPE 1 byte 1 byte L bytes 4F 01 to IO Application identifier (AID) P 50 00 to IO Application label P 51 00 to 7E Path P 52 04 to 7F Command to perform, see ISO/IEC 7816-4 P 53 00 to 7F Discretionary dat

4、a P 73 00 to 7F Discretionary ASN. 1 objects C 61 03 to 7F Application template C TYPE : P = primitive ASN.l object, C = constructed ASN.l object All other application class tags are reserved by IS0 5.2 Application identifier The AID is coded using hexadecimal notation. The most significant 4 bits o

5、f the first byte are the registration category (see table 2), which is used to OISO/IEC ISOhEC 7816-5 : 1994 (E) differentiate registered and proprietary application identifiers. Table 2 - Registration category values As defined in IS0 7812 II II IA I International registration II II lB I Reserved f

6、or IS0 II c I Reserved for IS0 II II ID I National registration II Reserved for IS0 II II IF I Proprietary non-registered II The PIX allows an application provider to identify their application(s). The PIX has a free coding. If the AID is 16 bytes long, then the value FF for the least significant by

7、te is reserved for future use. 5.2.1 Registration category = 0 to 9 The first part of the AID is the IIN (The registration category is the first digit of the IIN). If the IIN contains an odd number of digits, it shall be padded with F ( i.e. bit 4 to bit 1 of the least significant byte shall be set

8、to 1). If a PIX is present, it shall be preceded by a byte coded as FF. The coding of the AID is therefore IIN, FF as defined in IS0 7812 Proprietary application identifier extension W) length not defined in I 1 5.2.2 Registration category = A The RID consists of the following fields - Registration

9、category : 4 bits, coded as 1010. - Registered application provider number, 36 bits as 9 BCD digits. Other codings are reserved for IS0 use. The coding of the AID is therefore : Registered application provider identifier (RID) Proprietary application identifier extension I I I W) 5.2.3 Registration

10、category = D The RID consists of the following fields - Registration category : 4 bits, coded as 1101. - Country code of the national registration authority, 12 bits as 3 BCD digits, coded according to IS0 3166, numeric part only. - Field(s) specified by the national authority, 24 bits, BCD coding r

11、ecommended. The coding of the AID is therefore : 5.2.4 Registration category = F The coding of the remaining part of the AID is F lroprietary-the format of the AID.is therefore : Proprietary application identifier I WARNING Within the category F, where identifiers are not registered, the same value

12、of the AID may be used by different application providers. 5.2.5 Registration category = B,C,E These values are reserved for ISO. 5.3 Additional data elements In addition to the application identifier, the following data elements may be used for the application selection. 5.3.1 Application label Thi

13、s data element of free coding may be specified by an application provider for use at the man-machine interface, e.g. trademark to be displayed to the customer. Application label 1 1 5.3.2 Path The number of bytes of this data element is even. Path I 1 1 I I i 1 I 3 OISO/IEC ISO/IEC 7816-5 : 1994 (E)

14、 5.3.3 Command to perform The command to perform data element is a command APDU relevant to application selection. Command to perform, see ISO/IEC 7816-4 I 1 ( 5.3.4 Discretionary data The application provider may put any relevant data in this data element. Discretionary data 1 c - variable from 0 t

15、o 127 bytes- 1 OR I Discretionary ASN. 1 objects I I I 53.5 Application template The application template shall contain one or more of the ASN.1 objects relevant to an application. Within the application template, - the ASN.l object containing the application identifier is mandatory, - all other ASN

16、.l objects defined in this part of lSO/IEC 7816 are optional. ASN.l objects relevant to an application I I 5.4 Retrieval of ASN.l objects The ASN.l objects defined in this part of ISO/IEC 7816 may be found: - In the historical bytes of the ATR, - In a DIR file, - In the ATR file, - In any command or

17、 response message where ASN.l is used, e.g. in the file control information of a file, see ISO/IEC 7816-4. The DIR file contains only a sequence of application identifiers and/or application templates. Erased ASN.1 objects may be replaced by a sequence of 00 or FF bytes. If present in the historical

18、 bytes of the ATR, the tag and length of the ASN.1 object containing the AID shall be coded according to ISO/IEC 7816-4. 6 Use of the data elements 6.1 Application identification The application identification shall enable the IFD - To ascertain that an application may be initiated in the card ; - T

19、o identify the access method to a specific application in the card. 6.2 Retrieval of the application identifier If application identifier retrieval is offered by the card, the application identifier(s) may be read in the DIR file(s), and/or ATR file, as defined in ISO/IEC 7816-4. For single applicat

20、ion cards, the AID may be found in the historical bytes. NOTE 2 See ISO/IEC 7816-4 for the coding conven- tions in the historical bytes. 6.3 Application selection A card shall support one or more of the following application selection methods : - Direct application selection with AID; - Application

21、selection by the use of a DIR file or an ATR file; - Implicit application selection. 6.3.1 Direct application selection with AID Direct application selection is performed by the use of the SELECT FILE command, specifying the AID as dedicated file name. If this mechanism is supported by the card, the

22、n the IFD may explicitly select an application to be performed, without previously checking that the respective application is present in the card. If the respective application is not present, then the card shall reject the command. If the application is present, the card shall execute the SELECT F

23、ILE command according to ISO/IEC 7816-4. 6.3.2 Selection by the use of a DIR file or an ATR file A DIR file contains a sequence of application template ASN.l objects, or AID ASN.l objects. Such sequences may be present in the AIR file. The contents of the DIR file and/or ATR file determine which com

24、mand(s) shall be performed in order to select the application : - a (set of) SELECT FILE command(s) - a (set of) command(s) OISO/IEC 6.3.3 Implicit application selection An application may be selected implicitly after ATR and possible PTS. This is indicated in the historical bytes, see ISO/IEC 7816-

25、4. When the AID is present in the historical bytes, it denotes the implicitly selected application. NOTE 3 The implicit application selection is not recommended for multi-application cards. 6.4 Use of the command to perform ASN.l object. This ASN.l object contains a command message relevant to appli

26、cation selection. If several such objects are related to an application, the commands shall be performed in the order presented. 7 Registration of identifiers 7.1 Request for assignment of RIDS A named and identified application provider may make a request to its national standards body for the assi

27、gnment of a RID using the registration form shown in annex A. In the absence of a national standards body, the request shall be made to the secretariat of the IS0 technical body responsible for this part of ISO/IEC 7816. The national standards body (or the secretariat of the IS0 technical body respo

28、nsible for this part of ISO/IEC 7816 as appropriate), then acts as “the sponsoring authority” (see 7.2) in respect of the request. 7.2 Sponsoring authorities 7.2.1 Requests for assignment Requests for the assignment of RIDS may be forwarded to the registration authority (see 7.3) by the following bo

29、dies: - any member body of ISO; - the IS0 technical body responsible for this part of ISO/IEC 7816; - any organization authorized by IS0 for purposes concerned with the RIDS. ISO/IEC 7816-5 : 1994 (E) 7.2.2 Responsibilities of the sponsoring authorities The responsibilities of the sponsoring authori

30、ties shall be a) to receive registration forms for RIDS from within their countries or areas of responsibility; b) to forward to the registration authority those requests for a RID which are in compliance with this part of ISO/IEC 7816. 7.3 Registration authority For the purpose of this part of ISO/

31、IEC 7816 and according to the rules for the designation and operation of registration authorities in the IS0 Directives, the IS0 Council has designated : KTAS ISO/IEC 7816-5 Registration authority Teglholmsgade 1 DK- 1790 Copenhagen V to act as registration authority. With regard to the initial assi

32、gnment of RIDS, changes and deletions of RIDS and subsequent additions to the register, the responsibilities of the registration authority shall be 4 b) cl d) 7.4 to allocate the application provider number, to register the RID and to notify the sponsoring authority as to the disposition of the requ

33、est; to maintain a register of the identifiers assigned to application providers; to submit annually, to the secretariat of the IS0 technical body responsible for this part of ISO/IEC 7816, a copy of this register. The form in which this copy shall be provided shall be agreed upon by the registratio

34、n authority and the secretariat of the IS0 technical body responsible for this part of ISO/IEC 7816. to make available upon request a copy of the register to national standard bodies. Such copies are for the exclusive use of national standard bodies and should not be distributed to third parties. Re

35、gistration Management Group (RMG) A group shall be established to form the Registration Management Group (RMG). The responsibilities of the Registration Management Group shall be as resolved by the IS0 technical body responsible for this part of ISO/IEC 7816. ISO/IEC 7816-5 : 1994 (E) Annex A (norma

36、tive) Request registration form for a registered application provider identifier This request is submitted in accordance with International Standard ISO/IEC 78164, identification cards - Integrated circuit(s) cards with contacts - Numbering system and registration procedure for application identifie

37、rs. A.1 To be completed by the requesting organization Name of organization Address to be registered Principal contact in organization Telephone number Fax number Address for correspondence/billing Date Signature A.2 To be completed by national standards body Request received by A.3 To be completed

38、by ISO/IEC 7816-5 registration authority Registered application provider identifier Date Signature OISO/IEC ISO/IEC 7816-5 : 1994 (E) Annex B (informative) National numbering systems for applications in integrated circuit(s) cards B.l Introduction Registration category value D has been assigned for

39、use by national standards bodies in order to establish national numbering systems for applications in integrated circuit(s) cards. B.2 Operation of national numbering systems National standards bodies are advised to establish rules by means of national standards or other methods, for identifying app

40、lications in integrated circuit(s) cards in a national numbering system. They are also recommended to make arrangements for the administration of the system, including the procedures to be adopted for application providers, when the application providers make a request for and are assigned RIDS in a

41、ccordance with the rules, and the maintenance of a register of assigned RIDS (copies of which should be supplied at regular intervals to the registration authority at no cost). To this end, they may wish to appoint a responsible organization to act as their agents in the administration and maintenan

42、ce of the system within their countries. 8.3 Contact with the registration authority National standards bodies that intend to set up national numbering systems for applications in integrated circuit(s) cards are asked to notify the registration authority accordingly and to supply that authority with

43、 details of the national procedures for the assignment of numbers, the method used to identify applications in integrated circuit(s) cards, and the name of the organization administering the system. NOTE Where no national standards body exists, or if the national standards body is unable or unwillin

44、g to establish a national numbering system, application providers in that country may apply to the secretariat of the IS0 technical body responsible for this part of ISO/IEC 7816 for assistance in finding a national standards body from among its member bodies to volunteer to support those user needs

45、. B.4 Role of registration management wow The registration management group in the IS0 technical body responsible for this part of ISO/IEC 7816 shall, on request, provide advice and counsel to any national standards body on the national numbering system. ISO/IEC 7816-5:1994(E) 8 ISO/IEC KS 35.240.40 Descriptors: data processing, data storage devices, identification cards, ic cards, identification methods, international identification number, organizations for code assignment. Price based on 7 pages