Disclosure to Promote the Right To Information

Whereas the Parliament of India has set out to provide a practical regime of right to information for citizens to secure access to information under the control of public authorities, in order to promote transparency and accountability in the working of every public authority, and whereas the attached publication of the Bureau of Indian Standards is of particular interest to the public, particularly disadvantaged communities and those engaged in the pursuit of education and knowledge, the attached public safety standard is made available to promote the timely dissemination of this information in an accurate manner to the public.

इंटरनेट मानक

“!ान $ एक न' भारत का +नम-ण”Satyanarayan Gangaram Pitroda

“Invent a New India Using Knowledge”

“प0रा1 को छोड न' 5 तरफ”Jawaharlal Nehru

“Step Out From the Old to the New”

“जान1 का अ+धकार, जी1 का अ+धकार”Mazdoor Kisan Shakti Sangathan

“The Right to Information, The Right to Live”

“!ान एक ऐसा खजाना > जो कभी च0राया नहB जा सकता है”Bhartṛhari—Nītiśatakam

“Knowledge is such a treasure which cannot be stolen”

“Invent a New India Using Knowledge”

है”ह”ह

IS 14202-5 (2003): Identification Cards - IntegratedCircuit(s) Cards With Contacts, Part 5: Numbering Systemand Registration Procedure for Application Identifiers[LITD 16: Computer Hardware, Peripherals and IdentificationCards]

IS 14202 (Part 5) :2003lSO/lEC 7816-5:1994

VT?7%? J7TW7

W?mFPi3 – FiwhTRaaw$’lpd-mm

wl-JT5*~i3*zjim*qd Timhuiiulgfann

Indian Standard

IDENTIFICATION CARDS — INTEGRATEDCIRCUIT(S) CARDS WITH CONTACTS

PART 5 NUMBERING SYSTEM AND REGISTRATIONPROCEDURE FOR APPLICATION IDENTIFIERS

ICS 35.240

@ BIS 2003

BUREAU OF INDIAN STANDARDSMANAK BHAVAN, 9 BAHADUR SHAH ZAFAR MARG

NEW DELHI 110002

December 2003 Price Group 4

Computer Hardware Sectional Committee, LTD 37

NATIONAL FOREWORD

This Indian Standard ( Part 5 ) which is identical with lSO/lEC 7816-5 : 1994 ‘identification cards —Integrated circuit(s) cards with contacts — Part 5 : Numbering system and registration procedurefor application identifiers’ issued by the International Organizataion for Standardization ( ISO ) andInternational Electrotechnical Commission ( IEC ) jointly was adopted by the Bureau of Indian Standardson the recommendations of the Computer Hardware Sectional Committee and approval of the Electronicsand Telecommunication Division Council.

The text of International Standard has been proposed to be approved as suitable for publication as anIndian Standard without deviations. Certain terminology and conventions are, however, not identical tothose used in Indian Standards. Attention is particular drawn to the following:

Wherever the words ‘International Standard’ appear, referring to this standard, they should be readas ‘Indian Standard’.

CROSS REFERENCES

In this adopted standard, reference appears to certain International Standards for which IndianStandards also exist. The corresponding Indian Standards which are to be substituted in their place arelisted below along with their degree of equivalence for the editions indicated:

International Standard Corresponding Indian Standard Degree of Equivalence

ISO 7812 : 1987 Identification IS 14173 ( Part 1 ) :2003 ldentifica- Identicalcards — Numbering system and tion cards — Identification ofregistration procedure for issuer issuers: Part 1 Numbering systemidentifiers ( first revision)

ISO 7816-1 : 1987 Identificationcards — Integrated circuit(s) cardswith contacts — Part 1 : Physicalcharacteristics

lSO/lEC 7816-3:1989 Identificationcards — Integrated circuit(s) cardswith contacts — Part 3 : Electronicsignals and transmission protocols

IS 14202 ( Part 1 ) :2003 identifica-tion cards — Integrated circuit(s)cards with contacts: Part 1 Physicalcharacteristics ( first revision )

do

IS 14202 ( Part 3 ) :2003 ldentifica- dotion cards — Integrated circuit(s)cards with contacts: Part 3 Electronicsignals and transmission protocols

The concerned Technical Committee responsible for the preparation of this standard has reviewed theprovisions of the following International Publications and has decided that they are acceptable for usein conjunction with this standard:

International Publications Title

ISO 3166:1981 Codes for the representation of names of countries

lSO/l EC 8824:1990 Information technology — Open Systems Interconnection — Specificationof Abstract Syntax Notation One ( ASN.1 )

lSO/l EC 8825:1990 Information technology — Open Systems Interconnection — Specificationof Basic Encoding Rules for Abstract Syntax Notation One ( ASN.1 )

lSO/lEC 7816-4:1995 Identification cards — Integrated circuit(s) cards with contacts —Part 4: Interindustry commands for interchange

IS 14202 (Part 5) :2003lSO/lEC 7816-5:1994

hdku-1 standardIDENTIFICATION CARDS — INTEGRATED

CIRCUIT(S) CARDS WITH CONTACTSPART 5 NUMBERING SYSTEM AND REGISTRATION

PROCEDURE FOR APPLICATION IDENTIFIERS

1 Scope

This part of lSO/lEC 7816 specifies a numberingsystem for application identifiers and a registrationprocedure for application provider identifiers.

The numbering system described in this standardprovides a means for an application and relatedservices offered by a provider to identify if a givencard contains the elements required by its applicationand related services.

An application identifier (AID) is used to address anapplication in the card.

This part of lSO/lEC 7816 specifies the coding ofapplication identifiers together with means andmechanisms for addressing application parts incards.

This part of lSO/lEC 7816 establishes the authoritiesand procedures to ensure and optimize the reliabilityof the corresponding registration.

2 Nonnative references

The following standards contain provisions which,through reference in this part of lSO/lEC 7816,constitute provisions to this standard, At the time ofpublication, the editions indicated were valid. Allstandards are subject to revision, and parties toagreements based on this part of lSO/lEC 7816 areencouraged to investigate the possibility of applyingthe most recent editions of the standards listedbelow. Members of IEC and ISO maintain registers ofcurrently valid International Standards.

ISO 3166: 1981, Codes for the representation ofnames of countries.

lSO/lEC 8824:1990, Information technology - OpenSystems Interconnection - Specification of AbstractSyntax Notation One (ASN. 1).

lSO/lEC 8825:1990, Information technology - OpenSystems Interconnection - Spewfication of BasicEncoding Rules for Abstract Syntax Notation One(ASN. 1).

1“S0 7812: 1987, Identification cards - Numberingsystem and registration procedure for issueridentifiers.

ISO 7816-1: 1987, Identification cards - Integratedcircuit(s) cards with contacts - Part 1: Physicalcharacteristics.

lSO/tEC 7816-3: 1989, /dentifkation cards -Integmted circuit(s) cards with contacts - Part 3:Electronic signals and transmission protocols.

lSO/lEC 7816-4:-1), Identification cards -Integrated circuit(s) cards with contacts - Part 4:Interindustry commands for interchange.

3 Definitions and abbreviations

For the purposes of this part of lSO/lEC 7816, thedefinitions given in iSO/lEC 7816-4, as well as thefollowing definitions, apply.

3.1 Definitions

3.1.1 application Identifier: A data elementwhich identifies an application in a card. Anapplication identifier may contain a registeredapplication provider identifier, If it contains either aregistered application provider identifier or an issueridentification number, then this identification isunambiguous.

3.1.2 application provider: An entity whichprovides those components of an application on acard required to perform the respective application.

I) To be published

IS 14202 (Part 5) :2003lSO/lEC 7816-5:1994

3.1.3 application label : A data element for use atthe man-machine interface.

3.1.4 application template : A data element,which may be present for example in a DIR file, andwhich contains one or more ASN. 1 object(s) relevantto an application.

3.1.5 ASN.1 object : ASN.1 objects are defined inlSO/lEC 8824, and their coding in lSO/tEC 8825.

NOTE1 The ASN.1 objects defined in this part oflSO/lEC 7816 are comprised of one byte oftag, followed by one byte of body length,followed by a body of at most 127 bytes. Thenumber of bytes in the body is given by thelength byte.

The body of a primitive ASN.I objectcontains a data element. The body of aconstructed ASN.1 object contains primitiveor constructed ASN.I objects.

3.1.6 ATR file : The answer to reset (ATR) file isan optional elementary file, as defined in lSO/lEC7816-4.

3.1.7 data element : As defined in lSO/lEC7816-4.

3.1.8 directory (DIR) file : An optional elementaryfile containing a list of applications supported by thecard, and optional related data elements defined inthis part of lSO/lEC 7816.

3.1.9 master file : As defined in lSO/lEC7816-4.

3.1.10 path : As defined in lSO/lEC 7816-4. In thispart of lSO/lEC 7816, all paths commence with themaster file.

3.2 Abbreviations

AIDASN. I

ATR

BCDIFD

IIN

Plx

PTS

RID

Application identifier.

Abstract Syntax Notation 1, as definedin ISO 8824.Answer-to-Reset, as defined inlSO/lEC 7816-3.Binary coded decimal.

Interface device, as defined inlSO/lEC 7816-3.Issuer identification number,as defined in ISO 7812.Proprietary application identifierextension.Protocol type selection, as definedin lSO/lEC 7816-3.Registered application provideridentifier.

4 Data elements for applicationidentification and seiection

The following data elements are defined in this patiof lSO/iEC 7816:

- The application identifier (AID) comprised ofeither the registered application provider

5

5.1

identifie~ (RID) a’n”d optionally theproprietary application identifierextension (PIX)

or the proprietary application identifier;

The application label;The path to a file;A command to perform;Discretionary dataThe application template.

Coding of the data eiements

Structure of an ASN.1 object

If a data element defined in this clause isrepresented as an ASN.1 object, it shall be encodedaccording to table 1.

Table 1- ASN.1 coding of data elements

TAG LENGTH(L) VALUE(data element) TYPE1 byte 1 byte L bytes

‘4F’ ’01’ to ‘lo’ Applicationidentifier (AID) P

’50’ ’00 to ‘lo’ Application label P

’51‘ ’00’ to ‘7E’ Path P

’52’ ’04’ to ‘7F’ Command to perform,see ISOIIEC 7816-4 P

’53’ ’00to ‘7F’ Discretionary data P

,73, ’00to ‘7P DiscretionaryASN. 1 objects c

,6,, ’03’ to ‘7F’ Applicationtemplate c

TYPE: P = primitive ASN, 1 object,C = constructed ASN. 1 object

All other application class tags are resewed by ISO

5.2 Application identifier

The AID is coded using hexadecimal notation. Themost significant 4 bits of the first byte are theregistration category (see table 2), which is used to

differentiate registered and proprietary applicationidentifiers.

Table 2- Registration category values

II‘0’-’9’ I As defined in ISO 7812 II

‘D’ National registration

‘E’ Reserved for ISO

‘F’ Proprietary non-registered

The PIX allows an application provider to identifytheir application(s). The PIX has a free coding. If theAID is 16 bytes long, then the value ‘FF’ for the leastsignificant byte is reserved for futureuse.

5.2.1 Registration category = ‘O’to ‘9’

The first part of the AID is the IIN (The registrationcategory is the first digit of the IIN).

If the IIN contains an odd number of digits, it shall bepadded with ‘F ( i.e. bit 4 to bit 1 of the leastsignificant byte shall be set to 1).

If a PIX is present, it shall be preceded by a bytecoded as ‘FF’.

The coding of the AID is therefore :

< -----–- At) DliCatiOn identi

IIN, ‘FF’as defined in ISO 7812

length not defined in<- lSO/l EC 7816 -–>

!r (AID) -------- >

Proprietaryapplication

identifier extension(Plx)

\ <------------2to1’6W@ -------------> I

5.2.2 Registration category = ‘A

The RID consists of the following fields :

- Registration category :4 bits, coded as 1010.

- Registered application provider number, 36bits as 9 BCD digits. Other codings arereserved for ISO use.

The coding of the AID is therefore :

IS 14202 (Part 5) :2003lSO/lEC 7816-5:1994

5.2.3 Registration 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, codedaccording to ISO 3166, numeric part only.

- Field(s) specified by the national authority, 24bits, BCD coding recommended.

The coding of the AID is therefore:

~

-------Application identifier (AID) -------->

I .---5 b~es -----> I <--- s 11 b~es --->1

5.2.4 Registration category = ‘F’

The coding of the remaining part of the AID isproprietary, the format of the AID is therefore:

< -------Application identifier (AID) -------->

Proprietary application identifier4

I <------------1 to 16 b~es------------- ,1

WARNING VVNhinthe category ‘F’, where identifiersare not registered, the same value ofthe AID may be used by differentapplication 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 followingdata elements may be used for the applicationselection.

5.3.1 Application label

This data element of ftee coding maybe specified byan application provider for use at the man-machineinterface, e.g. trademark to be displayed to thecustomer.

I Application label II <------------ () to 16 bfies ------------- > I

5.3.2 Path

The number of bytes of this data element is even.

< –-––––- Application identifier (AID) -------- > I Path,Registered application Proprietary applicationprovider identifier (RID) identifier extension

(Plx)

i<-- -----variable from Oto 126 bytes ------->

I <-.---5 b~es ----- > \ < ----s11 b~es ---> I

3

IS 14202 (Part 5): 2003lSO/lEC 7816-5:1994

5.3.3 Command to perform

The ‘command to perform’ data element is acommand APDU relevant to application selection.

I Command to pedorm, see lSO/lEC 7816-4 II <------- variable from 4 to 127 bytes ------- > I

5.3.4 Discretionary data

The application provider may put any relevant data inthis data element.

Discretionary data

] <------- variable from () to 127 bytes ------- > I

OR

Dkcretionary ASN.1 objects

I <------- variable fromo to127 bytes ------- > I

5.3.5 Application template

The application template shall contain one or more ofthe ASN.1 objects relevant to an application. W}thinthe application template,

- the ASN. 1 object containing the applicationidentifier is mandatory,

- all other ASN. 1 objects defined in this parl oflSO/lEC 7816 are optional.

I ASN. 1 objects relevant to an application II <------- variable from 3 to 127 byes ------- > I

5.4 Retrieval of ASN.1 objects

The ASN.1 objects defined in this part of lSO/lEC7816 maybe found:

- In the historical bytes of the ATR,- In a DIR file,- In the ATR file,- In any command or response message where

ASN. 1 is used, e.g. in the file controlinformation of a file, see lSO/lEC 7816-4,

The DIR file contains only a sequence of applicationidentifiers and/or application templates. ErasedASN.1 objects may be replaced by a sequence of’00 or ‘FF’ bytes.

If present in the historical bytes of the ATR, the tagand length of the ASN. 1 object containing the AIDshall be coded according to lSO/lEC 7816-4.

6 Use of the data elements

6.1 Application identification

The application identification shall enable the IFD

- To ascerlain that an application may beinitiated in the card ;

- To identify the access method to a specificapplication 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 DIRfile(s), and/or ATR file, as defined in ISO/lEC7816-4.

For single application cards, the AID may be found inthe historical bytes.

NOTE2 See lSO/lEC7816-4 for the coding conven-tions in the historical bytes.

6.3 Application selection

A card shall support one or more of the followingapplication selection methods:

- Direct application selection with AID;- Application 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 useof the SELECT FILE command, specifying the AIDas dedicated file name.

If this mechanism is supported by the card, then theIFD may explicitly select an application to beperformed, without previously checking that therespective application is present in the card.

If the respective application is not present, then thecard shall reject the command.

If the application is present, the card shall executethe SELECT FILE command according to lSO/lEC7816-4.

6.3.2 Selection by the use of a DIR fileor an ATR file

A DIR file contains a sequence of applicationtemplate ASN.I objects, or AID ASN.1 objects. Suchsequences may be present in the ATR file.

The contents of the DIR file and/or ATR filedetermine which command(s) shall be performed inorder to select the application:

- a (set 09SELECT FILE command(s)

- a (set 09command(s)

4

6.3.3 Implicit application selection

An applicationmay be seiected implicitlyafter ATRand possibie PTS. This is indicated in the historicalbytes, see iSO/iEC 7816-4.

When the AiD is present in the historical bytes, itdenotes the implicitly seiected application.

NOTE 3 The implicit application selection is not

recommended for multi-application cards.

6.4 Use of the ‘command to perform’ ASN.Iobject.

This ASN. 1 object contains a command messagerelevant to application seiection. if severai suchobjects are reiated to an application, the commandsshall be performed in the order presented.

7 Registration of identifiers

7.1 Request for assignment of RIDs

A named and identified application provider maymake a request to its nationai standards body for theassignment of a RiD using the registration formshown in annex A.

in the absence of a nationai standards body, therequest shall be made to the secretariat of the iSOtechnical body responsible for this part of iSO/iEC7816. The nationai standards body (or the secretariatof the iSO technicai body responsible for this part ofiSO/iEC 7816 as appropriate), then acts as “thesponsoring authority” (see 7J2) in respect of therequest.

7.2 Sponsoring authorities

7.2.1 Requests for assignment

Requests for the assignment of RiDs may beforwarded to the registration authority (see 7.3) bythe following bodies:

# - any member body of iSO;- the iSO technicai body responsible for this part

of iSO/iEC 7816;

- any organization authorized by iSO for!purposes concerned with the RiDs.

7.2.2

The

iS 14202 (Part 5) :2003iSO/iEC 7816-5:1994

Responsibilities of the sponsoringauthorities

responsibiiities of the sponsoring authoritiesshaii be

a) to receive registration forms for RiDs fromwithin their countries or areas of responsibiiity;

b) to forward to the registration authority thoserequests for a RiD which are in mmpiiancewith this pariofiSO/fEC7816.

7.3 Registration authority

For the purpose of this part of iSO/iEC 7816 andaccording to the ruies for the designation andoperation of registration authorities in the iSODkectives, the iSO Counai has designated :

KTAS

iSO/iEC 7816-5 Registration authority

Tegihoimsgade 1

DK-1 790 Copenhagen V

to act as registration authority,

With regard to the initial assignment of RiDs,changes and deietions of RiDs and subsequentadditions to the register, the responsibiiities of theregistration authority shaii be

a)

b)

c)

d)

7.4

to aiiocate the application provider number, toregister the RiD and to notify the sponsoringauthority as to the disposition of the request;to maintain a register of the identifiersassigned to application providers;to submit annuaiiy, to the secretariat of theiSO technicai body responsible for this part ofiSO/iEC 7816, a copy of this register. The formin which this copy shaii be provided shaii beagreed upon by the registration authority andthe secretariat of the iSO technicai bodyresponsible for this part of iSO/iEC 7816.to make avaiiabie upon request a copy of theregister to nationai standard bodies, Suchcopies are for the exciusive use of nationaistandard bodies and shouid not be distributedto third pariies.

Registration Management Group (RMG)

A group shaii be established to form the RegistrationManagement Group (RMG).

The responsibiiities of the Registration ManagementGroup shaii be as resoived by the iSO technicai bodyresponsible for this part of iSO/iEC 7816.

5

IS 14202 (Part 5) :2003lSO/lEC 7816-5: 1994

Annex A(normative)

registration form for a registered

This request is submitted in accordance with International Standard lSO/lEC 7816-5, ldentjficatjoncards -Integrated circuit(s) cards with contacts - Numbering system and regktration procedure for applicationidentifiers.

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 by lSO/lEC 7816-5 registration authority

Registered application provider identifier

Date Signature

6

IS 14202 (Part 5) :2003lSO/lEC 7816-5:1994

Annex B(informative)

National numbering systems for applications

B.1 Introduction

Registration category value ‘D’ has been assigned foruse by national standards bodies in order to establishnational numbering systems for applicatioris inintegrated circuit(s) cards.

B.2 Operation of national numberingsystems

National standards bodies are advised to establishrules by means of national standards or othermethods, for identifying applications in integratedcircuit(s) cards in a national numbering system. Theyare also recommended to make arrangements for theadministration of the system, including theprocedures to be adopted for application providers,when the application providers make a request forand are assigned RIDs in accordance with the rules,and the maintenance of a register of assigned RIDs(copies of which should be supplied at regularintervals to the registration authority at no cost). Tothis end, they may wish to appoint a responsibleorganization to act as their agents in theadministration and maintenance of the system withintheir countries.

in integrated circuit(s) cards

B.3 Contact with the registrationauthority

National standards bodies that intend Ito set upnational numbering systems for applications inintegrated circuit (s) cards are asked to noti~ theregistration authority accordingly and to supply thatauthority with details of the national procedures forthe assignment of numbers, the method used toidentify applications in integrated circuit(s) cards, andthe name of the organization administering thesystem.

NOTEWhere no nationalstandardsbody exists, or if the

B.4

The

national standards body is unable or unwilling toestablish a national numbering system, applicationproviders in that country may apply to thesecretariat of the ISO technical body responsible forthis part of ISOIIEC 7816 for assistance in finding anational standards body from among its memberbodies to volunteer to support those user needs.

Role of registration managementgroup

registration management group in the ISOtechnical body respons~le for tfis part of lSO/lEC7816 shall, on request, provide advice and counsel toany national standards body on the nationalnumbering system.

7

Bureau of Indian Standards

BIS is a statutory institution established under the Bureau of Indian Standards Act, 1986 to promoteharmonious development of the activities of standardization, marking and quality certification of goods andattending to connected matters in the country.

Copyright

BI Shas the copyright of all its publications. No part of these publications maybe reproduced in any form withoutthe prior permission in writing of BIS. This does not preclude the free use, in the course of implementing thestandard, of necessary details, such as symbols and sizes, type or grade designations. Enquiries relating tocopyright be addressed to the Director (Publications), BIS.

Review of Indian Standards

Amendments are issued to standards as the need arises on the basis of comments. Standards are also reviewedperiodically; a standard along with amendments is reaffirmed when such review indicates that’no changes &eneeded; if the review indicates that changes are needed, it is taken up for revision. Users of Indian Standardsshould ascertain that they are in possession of the latest amendments or edition by referring to the latest issueof ‘BIS Catalogue’ and ‘Standards : Monthly Additions’.

This Indian Standard has been developed from Doc : No. LTD 37 ( 1934).

Amendments Issued SincePublication,

Amend No. Date of Issue Text Affected

BUREAU OF INDIAN STANDARDS

Headquarters:

Manak Bhavan, 9 Bahadur Shah Zafar Marg, New Delhi 110002Telephones: 23230131,23233375,2323 9402

Regional Offices :

Central: Manak Bhavan, 9 Bahadur Shah Zafar MargNEW DELHI 110002

Eastern : l/14 C. 1.T. Scheme VII M, V. I. P. Road, KankurgachiKOLKATA700 054

Northern: SCO 335-336, Sector 34-A, CHANDIGARH 160022

Southern :C. I. T. Campus, IV Cross Road, CHENNAI 600113

Western : Manakalaya, E9 MIDC, Marol, Andheri (East)MUMBAI 400093

Telegrams: Manaksanstha( Common to all offices)

Telephone

{

2323761723233841

{23378499,2337856123378626,23379120

{603843609285

{22541216,2254144222542519,22542315

{28329295,2832785828327891,28327892

Branches : AHMEDABAD. BANGALORE. BHOPAL. BHUBANESHWAR. COIMBATORE.FARIDABAD. GHAZIABAD. GUWAHATI. HYDERABAD. JAIPUR. KANPUR.LUCKNOW. NAGPUR. NALAGARH.PATNA. PUNE. RAJKOT. THIRWANANTHAPURAM.VISAKHAPATNAM.

Printed at New India Printing Press, Khurja, India