iso-iec 7816-4 (first edition 1995-09-01).htm

7816协议

<UL>
<LI><A HREF="iso7816_4.hmtl#ss8_1">8.1 Purpose and general structure</A></LI>
<LI><A HREF="iso7816_4.html#ss8_2">8.2 Category indicator (mandatory)</A></LI>
<LI><A HREF="iso7816_4.html#ss8_3">8.3 Optional COMPACT-TLV data objects</A>
<UL>
<LI><A HREF="iso7816_4.html#ss8_3_1">8.3.1 Country/issuer indicator</A></LI>
<LI><A HREF="iso7816_4.html#ss8_3_2">8.3.2 Card service data</A></LI>
<LI><A HREF="iso7816_4.html#ss8_3_3">8.3.3 Initial access data</A>
<UL>
<LI><A HREF="iso7816_4.html#ss8_3_3_1">8.3.3.1 Length='1'</A></LI>
<LI><A HREF="iso7816_4.html#ss8_3_3_2">8.3.3.2 Length='2'</A></LI>
<LI><A HREF="iso7816_4.html#ss8_3_3_3">8.3.3.3 Length='5'</A></LI>
</UL></LI>
<LI><A HREF="iso7816_4.html#ss8_3_4">8.3.4 Card issuer's data</A></LI>
<LI><A HREF="iso7816_4.html#ss8_3_5">8.3.5 Pre-issuing data</A></LI>
<LI><A HREF="iso7816_4.html#ss8_3_6">8.3.6 Card capabilities</A></LI>
</UL></LI>
<LI><A HREF="iso7816_4.html#ss8_4">8.4 Status information</A></LI>
<LI><A HREF="iso7816_4.html#ss8_5">8.5 DIR data reference</A></LI>
</UL>
<P>
<H2><A HREF="iso7816_4.html#ss9">9 Application-independent card services</A></H2>
<UL>
<LI><A HREF="iso7816_4.html#ss9_1">9.1 Definitions and scope</A></LI>
<LI><A HREF="iso7816_4.html#ss9_2">9.2 Card identification service</A></LI>
<LI><A HREF="iso7816_4.html#ss9_3">9.3 Application selection service</A>
<UL>
<LI><A HREF="iso7816_4.html#ss9_3_1">9.3.1 Implicit application selection</A></LI>
<LI><A HREF="iso7816_4.html#ss9_3_2">9.3.2 Direct application selection</A></LI>
</UL></LI>
<LI><A HREF="iso7816_4.html#ss9_4">9.4 Data object retrieval service</A></LI>
<LI><A HREF="iso7816_4.html#ss9_5">9.5 File selection service</A></LI>
<LI><A HREF="iso7816_4.html#ss9_6">9.6 File I/O service</A></LI>
</UL>
<P>
<H2><A HREF="iso7816_4.html#ssA">A Transportation of APDU messages by T=0</A></H2>
<UL>
<LI><A HREF="iso7816_4.html#ssA_1">A.1 Case 1</A></LI>
<LI><A HREF="iso7816_4.html#ssA_2">A.2 Case 2 Short</A>
<UL>
<LI><A HREF="iso7816_4.html#ssA_2S_1">A.2S.1 Le accepted</A></LI>
<LI><A HREF="iso7816_4.html#ssA_2S_2">A.2S.2 Le definitely accepted</A></LI>
<LI><A HREF="iso7816_4.html#ssA_2S_3">A.2S.3 Le not accepted, La indicated</A></LI>
<LI><A HREF="iso7816_4.htlm#ssA_2S_4">A.2S.4 SW1-SW2='9XYZ', except '9000'</A></LI>
</UL></LI>
<LI><A HREF="iso7816_4.htlm#ssA_3">A.3 Case 3 Short</A></LI>
<LI><A HREF="iso7816_4.html#ssA_4">A.4 Case 4 Short</A>
<UL>
<LI><A HREF="iso7816_4.html#ssA_4S_1">A.4S.1 Command not accepted</A></LI>
<LI><A HREF="iso7816_4.html#ssA_4S_2">A.4S.2 Command accepted</A></LI>
<LI><A HREF="iso7816_4.html#ssA_4S_3">A.4S.3 Command accepted with information added</A></LI>
<LI><A HREF="iso7816_4.html#ssA_4S_4">A.4S.4 SW1-SW2='9XYZ', except '9000'</A></LI>
</UL></LI>
<LI><A HREF="iso7816_4.html#ssA_5">A.5 Case 2 Extended</A>
<UL>
<LI><A HREF="iso7816_4.html#ssA_2E_1">A.2E.1 Le&lt;=256, B1='00', B2B3 from '0001' to '0100'</A></LI>
<LI><A HREF="iso7816_4.html#ssA_2E_2">A.2E.2 Le&gt;256, B1='00', B2B3=either '0000' or from '0101' to 'FFFF'</A></LI>
</UL></LI>
<LI><A HREF="iso7816_4.html#ssA_6">A.6 Case 3 Extended</A>
<UL>
<LI><A HREF="iso7816_4.html#ssA_3E_1">A.3E.1 0&lt;Lc&lt;256, B1='00', B2='00', B3!='00'</A></LI>
<LI><A HREF="iso7816_4.html#ssA_3E_2">A.3E.2 Lc&gt;255, B1='00', B2!='00', B3=any value</A></LI>
</UL></LI>
<LI><A HREF="iso7816_4.hmlt#ssA_7">A.7 Case 4 Extended</A>
<UL>
<LI><A HREF="iso7816_4.html#ssA_4E_1">A.4E.1 Lc&lt;256, B1='00', B2='00', B3!='00'</A></LI>
<LI><A HREF="ios7816_4.html#ssA_4E_2">A.4E.2 Lc&gt;255, B1='00', B2!='00', B3=any value</A></LI>
</UL></LI>
</UL>
<P>
<H2><A HREF="iso7816_4.html#ssB">B Transportation of APDU messages by T=1</A></H2>
<UL>
<LI><A HREF="iso7816_4.html#ssB_1">B.1 Case 1</A></LI>
<LI><A HREF="iso7816_4.html#ssB_2">B.2 Case 2 (short and extended)</A></LI>
<LI><A HREF="iso7816_4.html#ssB_3">B.3 Case 3 (short and extended)</A></LI>
<LI><A HREF="iso7816_4.html#ssB_4">B.4 Case 4 (short and extended)</A></LI>
</UL>
<P>
<H2><A HREF="iso7816_4.html#ssC">C Record pointer management</A></H2>
<UL>
<LI><A HREF="iso7816_4.html#ssC_1">C.1 Case 1</A></LI>
<LI><A HREF="iso7816_4.html#ssC_2">C.2 Case 2</A></LI>
</UL>
<P>
<H2><A HREF="iso7816_4.html#ssD">D Use of the basic encoding rules of ASN.1</A></H2>
<UL>
<LI><A HREF="iso7816_4.html#ssD_1">D.1 BER-TLV data object</A></LI>
<LI><A HREF="iso7816_4.html#ssD_2">D.2 Tag field</A></LI>
<LI><A HREF="iso7816_4.html#ssD_3">D.3 Length field</A></LI>
<LI><A HREF="iso7816_4.html#ssD_4">D.4 Value field</A></LI>
</UL>
<P>
<H2><A HREF="iso7816_4.html#ssE">E Examples of card profiles</A></H2>
<UL>
<LI><A HREF="iso7816_4.html#ssE_1">E.1 Introduction</A></LI>
<LI><A HREF="iso7816_4.html#ssE_2">E.2 Profile M</A></LI>
<LI><A HREF="iso7816_4.html#ssE_3">E.3 Profile N</A></LI>
<LI><A HREF="iso7816_4.html#ssE_4">E.4 Profile O</A></LI>
<LI><A HREF="iso7816_4.html#ssE_5">E.5 Profile P</A></LI>
<LI><A HREF="iso7816_4.html#ssE_6">E.6 Profile Q</A></LI>
</UL>
<P>
<H2><A HREF="iso7816_4.html#ssF">F Use of secure messaging</A></H2>
<UL>
<LI><A HREF="iso7816_4.html#ssF_1">F.1 Abbreviations</A></LI>
<LI><A HREF="iso7816_4.html#ssF_2">F.2 Use of cryptographic checksums</A></LI>
<LI><A HREF="iso7816_4.html#ssF_3">F.3 Use of cryptograms</A></LI>
<LI><A HREF="iso7816_4.html#ssF_4">F.4 Use of control references</A></LI>
<LI><A HREF="iso7816_4.html#ssF_5">F.5 Use of response descriptor</A></LI>
<LI><A HREF="iso7816_4.html#ssF_6">F.6 Use of the ENVELOPE command</A></LI>
</UL>
<HR>
<script type="text/javascript"><!--
google_ad_client = "pub-3768233548132609";
google_ad_width = 728;
google_ad_height = 90;
google_ad_format = "728x90_as";
google_ad_type = "text_image";
google_ad_channel ="";
//--></script>
<script type="text/javascript"
  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>

<H3><A NAME="ss1">1 Scope</A></H3>
<P>
This part of ISO/IEC 7816 specifies
<UL>
<LI>the contents of the messages, commands and responses, transmitted by the interface device to the card and conversely,</LI>
<LI>the structure and content of the historical bytes sent by the card during the answer to reset,</LI>
<LI>the structure of files and data, as seen at the interface when processing interindustry commands for interchange,</LI>
<LI>access methods to files and data in the card,</LI>
<LI>methods for secure messaging,</LI>
<LI>access methods to the algorithms processed by the card. It does not describe these algorithms.</LI>
</UL>
It does not cover the internal implentation within the card and/or the outside world.<BR>
It allows further standardization of additional interindustry commands and security architectures.<BR>
<P>
<H3><A NAME="ss2">2 Normative references</A></H3>
<P>
The following standards contain provisons which, through reference in this text, constitute provisions of this part of ISO 7816.
At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements
based 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 IEC and ISO maintain registers of currently valid International
Standards :
<P>
<B>ISO 3166</B>: 1993 Codes for the representation of names of countries.<BR>
<B><A HREF="iso7812_1.html">ISO/IEC 7812-1</A></B>: 1993 Identification cards - Identification of issuers - Part 1: Numbering system.<BR>
<B><A HREF="iso7816_3.html">ISO/IEC 7816-3</A></B>: 1989 Identification cards - Integrated circuit(s) cards with contacts - Part 3: Electronic signals and transmission protocols.<BR>
<B>Amendment 1</B>: 1992 to ISO/IEC 7816-3: 1989 Protocol type T=1, asynchronous half duplex block transmisson protocol.<BR>
<B>Amendment 2</B>: 1994 to ISO/IEC 7816-3: 1989 Revision of protocol type selection.<BR>
<B><A HREF="iso7816_5.html">ISO/IEC 7816-5</A></B>: 1994 Identification cards - Integrated circuit(s) cards with contacts - Part 5: Numbering system and registration procedure for application identifiers.<BR>
<B><A HREF="iso7816_6.html">ISO/IEC 7816-6</A></B>: Identification cards - Integrated circuit(s) cards with contacts - Part 6: Interindustry data elements.<BR>
<B>ISO/IEC 8825</B>: 1990 Information technology - Open Systems Interconnection - Specification of Basic Encoding Rules of Abstract Syntax Notation One (ASN.1)<BR>
<B>ISO/IEC 9796</B>: 1991 Information technology - Security techniques - Digital signature scheme giving message recovery.<BR>
<B>ISO/IEC 9797</B>: 1994 Information technology - Security techniques - Data integrity mechanism using a cryptographic check function employing a block cipher algorithm.<BR>
<B>ISO/IEC 9979</B>: 1991 Data cryptographic techniques - Procedures for the registration of cryptographic algorithms.<BR>
<B>ISO/IEC 10116</B>: 1991 Information technology - Modes of operation for an n-bit block cipher algorithm.<BR>
<B>ISO/IEC 10118-1</B>: 1994 Information technology - Security techniques - Hash-functions - Part 1: General<BR>
<B>ISO/IEC 10118-2</B>: 1994 Information technology - Security techniques - Hash-functions - Part 2: Hash-functions using an n-bit block cipher algorithm.<BR>

<H3><A NAME="ss3">3 Definitions</A></H3>
<P>
For the puposes of this part of ISO/IEC 7816, the following definitions apply :
<UL>
<LI><B>Answer-to-Reset file</B>: Elementary file which indicates operation characteristics of the card.</LI>
<LI><B>command-response pair</B>: Set of two messages a command followed by a response.</LI>
<LI><B>data unit</B>: The smallest set of bits which can be unambiguously referenced.</LI>
<LI><B>data object</B>: Information seen at the interface which consists of a tag, a length and a value (i.e. a data element).
In this part of ISO/IEC 7816, data objects are referred to as BER-TLV, COMPACT-TLV and SIMPLE-TLV data objects.</LI>
<LI><B>dedicated file</B>: File containing file control information and optionally memory available for allocation. It may be the parent of EFs and/or DFs.</LI>
<LI><B>DF name</B>: String of bytes which uniquely identifies a dedicated file in the card.</LI>
<LI><B>directory file</B>: Elementary file defined in <A HREF="iso7816_5.html">part 5 of ISO/IEC 7816</A>.</LI>
<LI><B>elementary file</B>: Set of data units or records which share the same file identifier. It cannot be the parent of another file.</LI>
<LI><B>file control parameters</B>: Logical, structural and security attributes of a file.</LI>
<LI><B>file identifier</B>: A 2-byte binary value used to address a file.</LI>
<LI><B>file management data</B>: Any information about a file except the file control parameters (e.g. expiration, date, application, label).</LI>
<LI><B>internal elementary file</B>: Elementary file for storing data interpreted by the card.</LI>
<LI><B>master file</B>: The mandatory unique dedicated file representing the root of the file structure.</LI>
<LI><B>message</B>: String of bytes transmitted by the interface device to the card or vice-versa, excluding transmission-oriented characters as defined in <A HREF="iso7816_3.html">part 3 of ISO/IEC 7816</A>.</LI>
<LI><B>parent file</B>: The dedicated file immediately preceding a given file within the hierachy.</LI>
<LI><B>password</B>: Data which may be required by the application to be presented to the card by its user.</LI>
<LI><B>path</B>: Concatenation of file identifier without delimitation. If the path starts with the identifier of the master file, it is an absolute path.</LI>
<LI><B>provider</B>: Authority who has or who obtained the right to create a dedicated file in the card.</LI>
<LI><B>record</B>: String of bytes which can be handled as a whole by the cards and referenced by a record number or by record identifier.</LI>
<LI><B>record identifier</B>: Value associated with a record that can be used to reference that record. Several records may have the same identifier within an elementary file.</LI>
<LI><B>record number</B>: Sequential number assigned to each record which uniquely identifies the record within its elementary file.</LI>
<LI><B>working elementary file</B>: Elementary file for storing data not interpreted by the card.</LI>
</UL>

<H3><A NAME="ss4">4 Abbreviations and notation</A></H3>
<P>
For the purposes of this part of the ISO/IEC 7816, the following abbreviations apply :
<P>
<TABLE BORDER=1>
<TR><TD><B>APDU</B></TD><TD>Application protocol data unit</TD></TR>
<TR><TD><B>ATR</B></TD><TD>Answer to reset</TD></TR>
<TR><TD><B>BER</B></TD><TD>Basic encoding rules of ASN.1 (see annex D)</TD></TR>
<TR><TD><B>CLA</B></TD><TD>Class byte</TD></TR>
<TR><TD><B>DIR</B></TD><TD>Directory</TD></TR>
<TR><TD><B>DF</B></TD><TD>Dedicated file</TD></TR>
<TR><TD><B>EF</B></TD><TD>Elementary file</TD></TR>
<TR><TD><B>FCI</B></TD><TD>File control information</TD></TR>
<TR><TD><B>FCP</B></TD><TD>File control parameter</TD></TR>
<TR><TD><B>FMD</B></TD><TD>File management data</TD></TR>
<TR><TD><B>INS</B></TD><TD>Instruction byte</TD></TR>
<TR><TD><B>MF</B></TD><TD>Instruction byte</TD></TR>
<TR><TD><B>P1-P2</B></TD><TD>Parameter bytes</TD></TR>
<TR><TD><B>PTS</B></TD><TD>Protocol type selection</TD></TR>
<TR><TD><B>RFU</B></TD><TD>Reserved for future use</TD></TR>
<TR><TD><B>SM</B></TD><TD>Secure messaging</TD></TR>
<TR><TD><B>SW1-SW2</B></TD><TD>Status bytes</TD></TR>
<TR><TD><B>TLV</B></TD><TD>Tag length value</TD></TR>
<TR><TD><B>TPDU</B></TD><TD>Transmission protocol data unit</TD></TR>
</TABLE>
<P>
For the purposes of this part of ISO/IEC 7816, the following notation applies :
<P>
<TABLE BORDER=1>
<TR><TD><B>'0'-'9' and 'A'-'F'</B></TD><TD>The sixteen hexadecimal digits</TD></TR>
<TR><TD><B>(B1)</B></TD><TD>Value of byte B1</TD</TR>
<TR><TD><B>B1||B2</B></TD><TD>Concatenation of bytes B1 (the most significant byte) and B2 (the least significant byte)</TD></TR>
<TR><TD><B>#</B></TD><TD>Number</TD></TR>
</TABLE>
<P>

<H3><A NAME="ss5">5 Basic organizations</A></H3>
<P>
<H4><A NAME="ss5_1">5.1 Data structures</A></H4>
This clause contains information on the logical structure of data as seen at the interface, when processing interindustry
commands for interchange. The actual storage location of data and structural information beyond what is described in this
clause are outside the scope of ISO/IEC 7816.
<P>
<H5><A NAME="ss5_1_1">5.1.1 File organization</A></H5>