ETSI TS 101 220 V8.2.0 (2008-08)
RTS/SCP-T070653v820
General Information
Standards Content (sample)
ETSI TS 101 220 V8.2.0 (2008-08)
Technical Specification
Smart Cards;
ETSI numbering system
for telecommunication application providers
(Release 8)
---------------------- Page: 1 ----------------------
Release 8 2 ETSI TS 101 220 V8.2.0 (2008-08)
Reference
RTS/SCP-T070653v820
Keywords
GSM, ID, smart card, UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.aspIf you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.aspCopyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI---------------------- Page: 2 ----------------------
Release 8 3 ETSI TS 101 220 V8.2.0 (2008-08)
Contents
Intellectual Property Rights................................................................................................................................4
Foreword.............................................................................................................................................................4
1 Scope........................................................................................................................................................5
2 References................................................................................................................................................5
2.1 Normative references.........................................................................................................................................5
2.2 Informative references........................................................................................................................................7
3 Definitions and abbreviations...................................................................................................................7
3.1 Definitions..........................................................................................................................................................7
3.2 Abbreviations.....................................................................................................................................................7
4 Structure of the Application IDentifier (AID)..........................................................................................8
4.1 Registered application provider IDentifier (RID)...............................................................................................8
4.2 Proprietary application Identifier eXtension (PIX) ............................................................................................8
5 Use of the Application IDentifier (AID) ..................................................................................................9
6 Toolkit Application Reference (TAR) .....................................................................................................9
7 Tag-Length-Value (TLV) data objects...................................................................................................10
7.1 TLV data object forms .....................................................................................................................................10
7.1.1 COMPREHENSION-TLV tag coding........................................................................................................10
7.1.1.1 Single byte format.................................................................................................................................11
7.1.1.2 Three-byte format.................................................................................................................................11
7.1.2 Length encoding.........................................................................................................................................11
7.2 Assigned TLV tag values .................................................................................................................................11
Annex A (normative): Allocated ETSI PIX numbers .......................................................................16
Annex B (normative): Coding of the PIX for GSM and TETRA applications ..............................17
Annex C (normative): Coding of the PIX for SIM toolkit API packages .......................................18
Annex D (normative): Allocated TAR values ....................................................................................19
Annex E (normative): Allocated 3GPP PIX numbers ......................................................................20
Annex F (normative): Coding of the PIX for 3G UICC applications .............................................21
Annex G (normative): Coding of the PIX for 3G USIM Toolkit Applications...............................22
Annex H (informative): Tag allocation guidelines...............................................................................23
Annex I (normative): Coding of the PIX for UICC toolkit API packages.....................................24
Annex J (normative): Coding of the PIX for (U)SIM API for Java Card™ packages.................25
Annex K (normative): Coding of the PIX for ISIM API for Java Card™ package.......................26
Annex L (Informative): Bibliography...................................................................................................27
Annex M (informative): Change history ...............................................................................................28
History ..............................................................................................................................................................31
ETSI---------------------- Page: 3 ----------------------
Release 8 4 ETSI TS 101 220 V8.2.0 (2008-08)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Smart Card Platform (SCP).
The contents of the present document are subject to continuing work within TC SCP and may change following formal
TC SCP approval. If TC SCP modifies the contents of the present document, it will then be republished by ETSI with
an identifying change of release date and an increase in version number as follows:
Version x.y.zwhere:
x the first digit:
0 early working draft;
1 presented to TC SCP for information;
2 presented to TC SCP for approval;
3 or greater indicates TC SCP approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI---------------------- Page: 4 ----------------------
Release 8 5 ETSI TS 101 220 V8.2.0 (2008-08)
1 Scope
The present document provides for the administration of shared name spaces in use by applications on the UICC
including the managed allocation of identifiers from these name spaces.2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.• For a specific reference, subsequent revisions do not apply.
• In the case of a reference to a TC SCP document, a non specific reference implicitly refers to the latest version
of that document in the same Release as the present document.• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.[1] Void.
[2] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[3] ISO/IEC 7816-4: "Identification cards - Integrated circuit cards - Part 4: Organization, security and
commands for interchange".[4] ITU-T Recommendation E.118: "The international telecommunication charge card".
[5] Void.[6] ETSI TS 151 011: "Digital cellular telecommunications system (Phase 2+); Specification of the
Subscriber Identity Module - Mobile Equipment (SIM-ME) interface (3GPP TS 51.011)".
[7] ETSI TS 101 267: "Digital cellular telecommunications system (Phase 2+); Specification of the
SIM Application Toolkit (SAT) for the Subscriber Identity Module - Mobile Equipment
(SIM-ME) interface (3GPP TS 11.14)".ETSI
---------------------- Page: 5 ----------------------
Release 8 6 ETSI TS 101 220 V8.2.0 (2008-08)
[8] ETSI TS 143 019: "Digital cellular telecommunications system (Phase 2+); Subscriber Identity
Module Application Programming Interface (SIM API) for Java Card; Stage 2 (3GPP TS 43.019)".
[9] ETSI EN 300 812-3: "Terrestrial Trunked Radio (TETRA); Subscriber Identity Module to Mobile
Equipment (SIM-ME) interface; Part 3: Integrated Circuit (IC); Physical, logical and TSIM
application characteristics".[10] ETSI TS 131 101: "Universal Mobile Telecommunications System (UMTS); UICC-terminal
interface; Physical and logical characteristics (3GPP TS 31.101)".[11] ETSI TS 131 102: "Universal Mobile Telecommunications System (UMTS); Characteristics of the
Universal Subscriber Identity Module (USIM) application (3GPP TS 31.102)".[12] ETSI TS 131 111: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Universal Subscriber Identity Module (USIM) Application
Toolkit (USAT) (3GPP TS 31.111)".[13] ETSI TS 131 114: "Universal Mobile Telecommunications System (UMTS); Universal Subscriber
Identity Module Application Toolkit (USAT) interpreter protocol and administration
(3GPP TS 31.114)".[14] ETSI TS 131 103: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Characteristics of the IP Multimedia Services Identity
Module (ISIM) application (3GPP TS 31.103)".[15] ISO/IEC 8825-1: "Information technology - ASN.1 encoding rules: Specification of Basic
Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules
(DER)".[16] ISO/IEC 7816-6: "Identification cards - Integrated circuit cards - Part 6: Interindustry data
elements for interchange".[17] ETSI TS 102 241: "Smart cards; UICC Application Programming Interface (UICC API) for Java
Card (TM) (Release 7)".[18] ETSI TS 131 130: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); (U)SIM Application Programming Interface (API);
(U)SIM API for Java Card (3GPP TS 31.130)".[19] ETSI TS 102 226: "Smart cards; Remote APDU structure for UICC based applications
(Release 6)".[20] ETSI TS 131 116: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Remote APDU Structure for (Universal) Subscriber
Identity Module (U)SIM Toolkit applications (3GPP TS 31.116)".[21] Void.
[22] ETSI TS 102 474: "Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Service
Purchase and Protection".[23] ETSI TS 102 223: "Smart Cards; Card Application Toolkit (CAT)".
[24] ETSI TS 131 133: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); IP Multimedia Services Identity Module (ISIM)Application Programming Interface (API); ISIM API for Java CardTM (3GPP TS 31.133 )".
[25] OMA-TS-Smartcard-Web-Server-V1-0 Available from http://www.openmobilealliance.org.
[26] ETSI TS 102 225: "Smart Cards; Secured Packet structure for UICC-based applications".
ETSI---------------------- Page: 6 ----------------------
Release 8 7 ETSI TS 101 220 V8.2.0 (2008-08)
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.[i.1] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905)".
3 Definitions and abbreviations3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Application IDentifier (AID): data element, which identifies an application in a card
NOTE: An AID may contain a Registered application provider IDentifier (RID). If it contains either a RID or an
issuer identification number, then this identification is unambiguous (see ISO/IEC 7816-4 [3]).
Application Provider (AP): entity, which provides those components of an application on a card, required to perform
the respective applicationNOTE: See ISO/IEC 7816-4 [3].
data object: structured data seen on an interface consisting of the concatenation of a mandatory tag field, a mandatory
length field and an optional value fieldtag: nominal datum that encodes the name of a data object
telecommunication IC card application: application described by an ETSI document
template: definition of a set of TLV data objects forming the value field of a constructed BER-TLV data object and a
data object that realizes this definitionToolkit Application Reference (TAR): data element, which identifies an application in the toolkit mechanisms
(e.g. SMS Data Download)3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AID Application IDentifier
AP Application Provider
API Application Program Interface
BCD Binary Coded Decimal
BER Basic Encoding Rules
CR Comprehension Required
DECT Digital Enhanced Cordless Telecommunications
GSM Global System for Mobile communication
IC Integrated Circuit(s)
ICC Integrated Circuit Card
ID IDentifier
ISIM IP Multimedia Services Identity Module
ETSI
---------------------- Page: 7 ----------------------
Release 8 8 ETSI TS 101 220 V8.2.0 (2008-08)
PIX Proprietary application Identifier eXtension
RFU Reserved for Future Use
RID Registered application provider IDentifier
SIM Subscriber Identity Module
TAR Toolkit Application Reference
TETRA TErrestrial Trunked RAdio
TLV Tag-Length-Value
UPT Universal Personal Telecommunications
URL Uniform Resource Locator
USAT USIM Application Toolkit
USIM Universal Subscriber Identity Module
USSD Unstructured Supplementary Services Data
4 Structure of the Application IDentifier (AID)
In accordance with ISO/IEC 7816-4 [3], the AID has the following structure:
<--------------------------- Application IDentifier (AID) ----------------------------->
Registered application provider IDentifier Proprietary application Identifier eXtension
(RID) (PIX)<--------------- 5 bytes ---------------->
<--------------- ≤ 11 bytes -------------->
Figure 4.1: AID structure
The AID consists of a Registered application provider IDentifier (RID) of 5 bytes and a Proprietary application
Identifier eXtension (PIX) of up to 11 bytes.4.1 Registered application provider IDentifier (RID)
The RIDs dealt with in the present document, as registered by ISO/IEC according to ISO/IEC 7816-4 [3], are:
• 'A000000009' for ETSI;• 'A000000087' for the 3GPP.
4.2 Proprietary application Identifier eXtension (PIX)
The PIX is used at the discretion of ETSI and can contain between 7 bytes and 11 bytes of information. The PIX is
coded in hexadecimal. Hexadecimal digit 1 is the most significant digit.Digits 1 to 4 Application code
Purpose: To be used for identification of the standardized ETSI or 3G card application
(e.g. GSM, DECT, UPT, pre-paid application). Different versions of anapplication may have individual codings.
Management: Assigned by ETSI on request from the ETSI or 3G technical body
responsible for the document in question.
ETSI
---------------------- Page: 8 ----------------------
Release 8 9 ETSI TS 101 220 V8.2.0 (2008-08)
Coding: Hexadecimal. The coding indicates the ETSI or 3G document that specifies
the standardized ETSI or 3G card application and the PIX number.The correspondence between digits 1 to 4 and the ETSI or 3G document in
question can be seen in a list maintained by the ETSI Secretariat (see
annex A). Escape value '0000' is reserved for use by the ETSI Secretariat for
proprietary ETSI or 3G applications.
Digits 5 to 8 Country code
Purpose: To indicate the country of the application provider of the ETSI or
3G standardized application.
Coding: According to ITU-T Recommendation E.164 [2]. The coding is right justified
and padded with 'F' on the left.NOTE: List of actual country codes is published by ITU.
Digits 9 to 14 Application provider code
Purpose: Individual code for the application provider of the ETSI or 3G standardized
application.Coding: According to ITU-T Recommendation E.118 [4]. Hexadecimal. The coding is
right justified and padded with 'F' on the left.
Digits 15 up to 22 Application provider field Optional. Up to 8 digits
Purpose: The use of this field is entirely up to the application provider. It may, for
instance, be used to indicate "local" versions, revisions, etc. of the ETSI or3G standardized application. According to ISO/IEC 7816-4 [3], if the AID is
16 bytes long, then the value 'FF' for the least significant byte (digits 21 and
22) is reserved for future use.
Management: Application provider.
Coding: Hexadecimal.
NOTE: Digits 1 to 14 are assigned and registered by the ETSI Secretariat upon request by the responsible ETSI
technical body.5 Use of the Application IDentifier (AID)
The use of the AID is specified in ISO/IEC 7816-4 [3].
6 Toolkit Application Reference (TAR)
The Toolkit Application Reference (TAR) is used to uniquely identify a second level application
(e.g. Toolkit Application).To be addressed, the Toolkit Application needs a first level application (e.g. GSM, USIM application) running.
A second level application may have several TAR values assigned.The TAR values in the range '00 00 01' to 'AF FF FF' and 'C0 00 00' to 'FF FF FF' are under the responsibility of the
first level application issuer.ETSI
---------------------- Page: 9 ----------------------
Release 8 10 ETSI TS 101 220 V8.2.0 (2008-08)
The TAR values '00 00 00' and in the range 'B0 00 00' to 'BF FF FF' are reserved for allocation (by the ETSI
Technical Body responsible for the present document) to generic second level application independent of the first level
application issuer.It is not mandatory for a second level application to have a TAR value assigned. If a TAR value is assigned to a second
level application it is not mandatory for this value to be included in the AID. As a consequence, the AID coding of the
second level application might not always comply with the present document (see annex B).
Table 6.1 lists the TAR values or range and their associated application categories.
Table 6.1: TAR and application categoriesToolkit application reference Application category
'00 00 00' and 'B2 01 00' Issuer security domain
'00 00 01' to 'AF FF FF' Allocated by the 1 level application issuer
'B0 00 00' to 'B0 FF FF' Remote File Management (see annex D)
'B1 00 00' to 'B1 FF FF' Payment application (see annex D)
'B2 00 00' to 'B2 00 FF' USAT Interpreter Application (see annex D)
'B2 01 01' and 'B2 01 02' Smart Card Web Server (see annex D)
'BF FF 00' to 'BF FF FF' Proprietary Toolkit Application
'C0 00 00' to 'FF FF FF' Allocated by the 1 level application issuer
7 Tag-Length-Value (TLV) data objects
7.1 TLV data object forms
The encoding of data objects shall consist of three components that appear in the following order:
1. Tag (T).2. Length (L).
3. Value (V).
The encoding of these components for each of the recognized forms of TLV is given in the following table.
Name of TLV Encoding of tag field Encoding of length field Encoding of value field
BER-TLV See ISO/IEC 8825-1 [15] See clause 7.1.2 See ISO/IEC 8825-1 [15]COMPACT-TLV See ISO/IEC 7816-4 [3] See ISO/IEC 7816-4 [3] See ISO/IEC 7816-4 [3]
COMPREHENSION-TLV See clause 7.1.1 See clause 7.1.2 See ISO/IEC 7816-4 [3]
7.1.1 COMPREHENSION-TLV tag coding
COMPREHENSION-TLV tags can be in one of two formats: single byte and three-byte format.
The value of the first byte identifies the format used.First byte value Format
'00' Not used
'01' to '7E' Single byte
'7F' Three-byte
'80' Reserved for future use
'81' to 'FE' Single byte
'FF' Not used
The same value in the different formats represents the same data object.
ETSI
---------------------- Page: 10 ----------------------
Release 8 11 ETSI TS 101 220 V8.2.0 (2008-08)
Unless otherwise stated, for COMPREHENSION-TLV it is the responsibility of the UICC application and the terminal
to decide the value of the Comprehension Required (CR) flag for each data object in a given command.
Handling of the CR flag is the responsibility of the receiving entity.CR Value
Comprehension required 1
Comprehension not required 0
7.1.1.1 Single byte format
The tag is coded over one byte.
8 7 6 5 4 3 2 1
CR Tag value
CR: Comprehension required for this object.
7.1.1.2 Three-byte format
The tag is coded over three bytes.
Byte 1 Byte 2 Byte 3
8 7 6 5 4 3 2 1
Tag value format = '7F' CR Tag value
Tag value format: Byte 1 equal to '7F' indicates that the tag is in the three-byte format.
• CR: Comprehension required for this object. Use and coding is the same as in single byte format.
• Tag value: Coded over 15 bits, with bit 7 of byte 2 as the most significant bit. Range is from '00 01' to '7F FF'.
7.1.2 Length encodingThe length is coded onto 1, 2, 3 or 4 bytes according to the following table:
Length Byte 1 Byte 2 Byte 3 Byte 4
0 to 127 Length ('00' to '7F') Not present Not present Not present
128 to 255 '81' Length ('80' to 'FF') Not present Not present
256 to 65 535 '82' Length ('01 00' to 'FF FF') Not present
65 536 to 16 777 215 '83' Length ('01 00 00' to 'FF FF FF')
7.2 Assigned TLV tag values
The assigned tag values given in the following tables are the tag values used by specifications referencing the present
document. All unassigned tag values are reserved for future use.COMPACT-TLV tag ATR data objects
'31' Card Service Data
'73' Card Capabilities
BER-TLV tag Templates
'61' Application Template
'62' FCP Template
'7B' Security Environment Template
ETSI
---------------------- Page: 11 ----------------------
Release 8 12 ETSI TS 101 220 V8.2.0 (2008-08)
BER-TLV tag FCP template ('62')
'80' File Size - Data
'81' File Size - Total
'82' File Descriptor
'83' File Identifier
'84' DF Name (AID)
'85' Proprietary - Primitive
'88' SFI Support
'8A' Life Cycle Status
Security attribute data object
'8B' Security Attribute - Reference Format
'8C' Security Attribute - Compact Format
'AB' Security Attribute Template - Expanded Format
Proprietary template
'A5' Proprietary Template
PIN Status data objects
'C6' PIN Status data objects
BER-TLV tag Security attribute template ('AB')
Access Mode data objects
'80' Access Mode - Generic Command
'81' - '8F' Access Mode - Command Description
'9C' Proprietary State Machine
Security Condition data objects
'90' Security Condition - ALWAYS
'97' Security Condition - NEVER
'9E' Security Condition - Security Condition Byte
'A4' Control reference Template
'A0' Security Condition - OR Template
'AF' Security Condition - AND Template
BER-TLV tag Control reference template ('A4')
'83' Key Reference
'95' Usage Qualifier
BER-TLV tag PIN Status data objects ('C6')
'83' Key Reference
'90' PIN Enabled/Disabled status byte(s)
'95' Usage Qualifier
BER-TLV Tag Proprietary template ('A5')
'80' UICC Characteristics
'81' Application Power Consumption
'82' Minimum Application Clock Freq.
'83' Amount of Available Memory
'84' File details
'85' Reserved file size
'86' Maximum file size
'87' Supported system commands
'88' Specific UICC environmental conditions
'C0' Special File Information
'C1' Filling Pattern
'C2' Repeat Pattern
ETSI
---------------------- Page: 12 ----------------------
Release 8 13 ETSI TS 101 220 V8.2.0 (2008-08)
BER-TLV tag Application template ('61')
'4F' Application Identifier (AID)
'50' Application Label
'51' Path
'52' Command to Perform
'53' Discretionary Data
'73' Discretionary Template
'5F50' Uniform Resource Locator (URL)
BER-TLV tag Discretionary template ('73') in EF DIR
'A0' EAP Application service specific data content tag
BER-TLV Tag Terminal capabilities template ('A9')
'80' Terminal power supply
'81' Extended logical channels terminal support
'82' Additional interfaces support
BER-TLV tag Card application toolkit templates
'CF' Reserved for proprietary use (direction terminal to UICC)
'D0' Proactive Command
'D1' GSM/3G/3GPP2 - SMS-PP Download
'D2' GSM/3G/3GPP2 - Cell Broadcast Download
'D3' Menu Selection
'D4' Call Control
'D5' GSM/3G - MO Short Message control
'D6' Event Download
'D7' Timer Expiration
'D8' Reserved for intra-UICC communication and not visible on the card interface
'D9' 3G – USSD Download
'DA' MMS Transfer status
'DB' MMS notification download
'DC' Terminal application tag
BER-TLV tag Remote Management Application Data templates
'AA' Command Scripting Template
'AB' Response Scripting Template
BER-TLV tag Command Scripting template ('AA')
'81' Immediate Action tag
'82' Error Action tag
'83' Script Chaining tag
BER-TLV tag Response Scripting template ('AB')
'80' Number of executed C-APDUs tag (for Release 6)
'80' Number of executed command TLV objects tag (for Release 7 onwards)
'81' Immediate Action Response tag
'83' Script Chaining Response tag
'90' Bad format tag
BER-TLV tag Manage Secure Channel command
'81' UICC_ID TLV
'82' Endpoint information TLV
'83' Term label – Terminal_ID TLV
'84' Term label – Terminal_appli_ID TLV
'85' Term label – UICC_Identifier TLV
'86' Term label – UICC_appli_ID TLV
'87' Master_SA TLV
'88' Connection_SA TLV
ETSI
---------------------- Page: 13 ----------------------
Release 8 14 ETSI TS 101 220 V8.2.0 (2008-08)
BER-TLV tag Transact Data command
'80' Encrypted data TLV
COMPREHENSION-TLV tag Tag value, bits 1-7
Card application toolkit data objects Length of tag
(CR and Tag value) (Range: '01' - '7E')
'01' or '81' Command details tag 1 '01'
'02' or '82' Device identity tag 1 '02'
'03' or '83' Result tag 1 '03'
'04' or '84' Duration tag 1 '04'
'05' or '85' Alpha identifier tag 1 '05'
'06' or '86' Address tag 1 '06'
'07' or '87' Capability configuration parameters tag 1 '0
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.