Application identifier

Referenced by a compact header set to ‘FY’ in the historical byte, or by tag ’4F’ in the initial data string (see 8.1.2), in EF.ATR, in EF.DIR and in the management data of any DF, this interindustry data element identifies an application.

An application identifier (AID) consists of up to sixteen bytes. Bits 8 to 5 of the first byte indicate a category according to Table 90.

Table 90 — Categories of application identifiers

 
Value Category Meaning
’0′ to ’9′ - Reserved for backward compatibility with ISO/IEC 7812-1[3] (see annex D)
‘A’ International International registration of application providers according to ISO/IEC 7816-5[4]
‘B’, ‘C’ - Reserved for future use by ISO/IEC JTC 1/SC 17
‘D’ National National (ISO 3166-1[1]) registration of application providers according to ISO/IEC 7816-5[4]
‘E’ Standard Identification of a standard by an object identifier according to ISO/IEC 8825-1
‘F’ Proprietary No registration of application providers

Figure 7 shows an international AID. It consists of a registered application provider identifier (international RID) on five bytes and optionally, a proprietary application identifier extension (PIX) on up to eleven bytes.

–The international RID shall uniquely identify an application provider (see ISO/IEC 7816-5[4]).

  • Bits 8 to 5 of the first byte shall be set to 1010, i.e., the first quartet shall be set to ‘A’.
  • Each one of the subsequent nine quartets shall be set from ’0′ to ’9′.

–The extension has a free encoding. It allows the application provider to identify its different applications.

Registered application provider identifier (International RID, five bytes, first byte set to ‘AX’) Proprietary application identifier extension (PIX, up to eleven bytes)
Figure 7 — International AID

Figure 8 shows a national AID. It consists of a registered application provider identifier (national RID) on five bytes and optionally, a proprietary application identifier extension (PIX) on up to eleven bytes.

–The national RID shall uniquely identify an application provider (see ISO/IEC 7816-5[4]).

• Bits 8 to 5 of the first byte shall be set to 1101, i.e., the first quartet shall be set to ‘D’.

     • The subsequent three quartets (from ’0′ to ’9′) shall form a country code (see ISO 3166-1[1]).

• The recommended value of each one of the last six quartets is from ’0′ to ’9′. ⎯ The extension has a free encoding. It allows the application provider to identify its different applications.

Registered application provider identifier (National RID, five bytes, first byte set to ‘DX’) Proprietary application identifier extension (PIX, up to eleven bytes)

Figure 8 — National AID

Figure 9 shows a standard AID. It consists of up to sixteen bytes. The first byte shall be set to 1110 1000, i.e., to ‘E8′. The values ‘E0′ to ‘E7′ and ‘E9′ to ‘EF’ are reserved for future use by ISO/IECJTC 1/SC 17. An object identifier (see ISO/IEC 8825-1) shall follow for identifying a standard specifying an application (see examples in annex A, e.g., ISO/IEC 7816-12[4], personal verification through biometric methods, ISO/IEC 7816-15[4], cryptographic information application). An application identifier extension (specified according to the identified standard) may follow for identifying different implementations.

‘E8′ Object identifier (see annex A) Application-specific application identifier extension

Figure 9 — Standard AID

Figure 10 shows a proprietary AID. It consists of up to sixteen bytes. Bits 8 to 5 of the first byte shall be set to 1111, i.e., to ‘F’. In the proprietary category, as application providers are not registered, different application providers may use the same AID.

Proprietary application identifier (Proprietary AID, up to sixteen bytes, first byte set to ‘FX’)

Figure 10 — Proprietary AID

Application template

Referenced by tag ’61′, this interindustry template may be present in EF.ATR, in EF.DIR and in the management data of any DF.

 Such a template shall contain one and only one application identifier. If several application identifiers are valid names for the same DF, then each one should be present in a different application template.

 Such a template may optionally contain other interindustry data objects relating to the application as listed in Table 91 and defined hereafter.

Table 91 — Interindustry data objects for application identification and selection

Tag Value
’4F’ Application identifier
’50′ Application label
’51′ File reference
’52′ Command APDU
’53′, ’73′ Discretionary data, discretionary template
’5F50′ Uniform resource locator (see IETF RFC 1738[19] and IETF RFC 2396[20])
’61′ Set of application-related data objects