1、IbSLibb 0820093 179 S BRITISH STANDARD Identification card systems - Inter-sector electronic purse Part 4: Data objects The European Standard EN 154641999 has the status of a British Standard ICs 35.240.15 NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW BS EN 154641999 e LbZVb
2、bS 0820092 OOLI II BS EN 1546-4:1999 National foreword This British Standard is the English language version of EN 15464 1999. The UK participation in its preparation was entrusted to Technical Committee IST/17, Identifcation cards and related devices, which has the responsibility to: This British S
3、tandard, having been prepared under the direction of the DISC Board, was published under the authority of the Standards Committee and comes into effect on 15 December 1999 - aid enquirers to understand the text; - present to the responsible European committee any enquiries on the - monitor related i
4、nternational and European developments and promulgate interpretation, or proposals for change, and keep the UK interests informed; them in the UK A list of organizations represented on this committee can be obtained on request to its secrem. Cross-references The British Standards which implement int
5、ernational or European publications referred to in this document may be found in the BSI Standards Catalogue under the section entitied “International Standards Correspondence Index“, or by using the “Find“ facility of the BSI Standards Electronic Catalogue. A British Standard does not purport to in
6、clude all the necessary provisions of a contract. Users of British hdards are responsible for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a hnt cover, an inside front cover, the EN t
7、itle page, pages 2 to 32, an inside back cover and a back cover. The BSI copyright notice displayed in this document indicates when the document was last issued. Amendments issued since publication I Amd. No. Date O BSI 12-1999 ISBN O 580 35214 5 EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN
8、1546-4 August 1999 ICs 35.240.1 5 English version Identification card systems - I nter-sector electronic purse - Part 4: Data objects Systmes de caties didentification - Porte-monnaie iectronique Intersectoriel - Partie 4: Objets de donnes Identiikatlonskatiensysteme - Branchenobergreiiende eiektron
9、kche Geldbrse -Teil 4 atenobjekte This European Standard was approved by CEN on 29 July 1999. CEN members are bound to compiy with the CENICENELEC Internal Regulations which stipulate the conditions for gMng this European Standard the status of a national standard without any alteration. Up-to-date
10、lists and bibiiographlcal references concerning such national standards may be obtained on application to the Central Secretariat or to any CEN member. This European Sandard exk in ihree official versh (English, French, German). A version in any other language made by transiain under the responsibil
11、ity of a CEN member into its own language and notified to the Centrai Secretariat has the same status as the official VerSionS. CEN members are the national standards bodies of Austria, Belgium, Czech Republic, Denmark, Finland, France, Oermany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlan
12、ds, Norway, Portugal, Spain, Sweden, Switzerland and United Kingdom. EUROPEAN C0MMlT“EE FOR STANDARDIZATION EUROPISCHES KOMITEE FOR NORMUNG COMITE EUROPEEN DE NORMALISATION Q 1999 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 154
13、641 999 E Page 2 EN 154641 999 Contents I 2 3 3.1 3.2 4 4 .I 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 I Page Scope . 4 Normative references 4 Definitions, symbols and abbreviations 5 Terms defined in prEN 1546-1 . 5 Symbols and abbrevations . 7 Description of the Dictionary mechanism . 7 Introduction . - 7 I
14、ndication of the use of TLV coding - 8 Structure of the headerlist 8 Coding of the Tag field -. 10 Coding of the length field .- Ir Coding of Data Elements . 14 Parsing a headerlist 15 Headerlist mapping .- 15 Reading out the Dictionary of an IEP . 14 Annex A (Informative) Examples of the use of hea
15、derlists 16 Annex B (Informative) Examples of Discretionary Data 31 Bibliography -. 32 . OBSI 12 1999 1bZLibh 0820095 813 m Page 3 EN 15464:1999 Foreword This European Standard has been prepared by Technical Committee CENTTC 224, Machine-readable cards, related device interfaces and operations, the
16、Secretariat of which is held by AFNOR This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by February 2000, and conflicting national standards shall be withdrawn at the latest by February 2000. According
17、 to the CENICENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Sp
18、ain, Sweden, Switzerland and the United Kingdom. This European Standard consists of the following parts, under the general title “Identification card systems - Inter-sector electronic purse”: - Part 1: Definitions, concepts and structures - Part 2: Security architecture - Part 3: Data elements and i
19、nterchanges - Part 4: Data objects O BSI 12 1999 B Lb2ilbb 08200b 75T Page 4 EN 154641 999 1 Scope This part of EN 1546 defines the Tag values required and describes the Dictionary mechanisms necessary for their utilization in order to achieve interoperability between IEP Systems where Data Elements
20、 have different lengths and/or the ordering of Data Elements in commands and responses is different from that defined in EN 1546-3. The mechanisms are based on TLV (Tag-length-value) definitions of each Data Element. Tags and mechanisms are also defined for handling Discretionary Data elements addit
21、ional to those defined in EN 1546-3. The TLV mechanisms used are in accordance with ASN.l. Examples of utilization of Dictionaries are described in an informative Annex. 2 Normative references This European Standard incorporates, by dated or undated reference, provisions from other publications. The
22、se normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to, or revisions of any of these publications apply to this European Standard only when incorporated in it by amendment or revision. For unda
23、ted references the latest edition of the publication referred to applies. EN I 546-1, Identification card systems - Inter-sector electronic purse - Part 1: Definitions, concepts and structures. EN 1546-2, Identification card systems - Inter-sector electronic purse - Part 2: Security architecture. EN
24、 1546-3:1995, Identification card systems - Inter-sector electronic purse - Part 3: Data elements and interchanges. EN IS0 3166-1 :I 997, Codes for the representation of names of countries and their subdivisions - Part i: Country codes (IS0 3166-l:i997). EN ISO/IEC 781 6-4:1996, Information technolo
25、gy - Identification cards - Integrated circuit(s) cards with contacts - Part 4: Interindustry commands for interchange (ISO/IEC 781 6-43 995). EN ISOAEC 7816-6:1997, Identification cards - Integrated circuit(s) cards with contacts - Part 6: Interindustry data elements (ISO/IEC 7816-6:1996). ISO/IEC
26、8825 (all parts), Information technology - ASN. 1 encoding rules. IS0 8859-1 : 1987, Information processing - card issuer; currency exchange; currency exchange log; identity; inter-sector electronic purse (IEP); IEP balance; IEP monitor; IEP system; load device; load log; load SAM; LSAM; purchase; p
27、urchase device; purchase log; purchase SAM; PSAM; purse provider SAM; PPSAM. In order to emphasize terms specific to a general IEP System, throughout this European Standard, these terms commence with capital letters, e.g. Purchase Log. 3.1.1 This part of EN 1546 uses the following terms defined in E
28、N 1546-2: a) completion code; b) signature. In order to emphasize terms specific to a general IEP System, throughout this European Standard, these terms commence with capital letters, e.g. Completion Code. Terms defined in EN 1546-2 OBSI 12 1999 Page 6 EN 1546-4:1999 3.1.2 Terms defined in EN 1546-3
29、 This part of EN 1546 uses the following terms defined in EN 1546-3: a) discretionary data. In order to emphasize terms specific to a general IEP System, throughout this European Standard, these terms commence with capital letters, e.g. Discretionary Data. 3.1.3 Terms specific to this part of EN 154
30、6 For the purpose of this standard, the following definitions apply: 3.1.3.1 constructed data object a data object where the value field itself is a data object (see EN ISO/IEC 7816-4:1996) 3.1.3.2 data element as defined in EN 1546-3. NOTE A data element may be presented in the value field of a dat
31、a object (see EN ISO/IEC 781641996). 3.1.3.3 data object a concatenation of the following string of bytes (see EN ISOAEC 78164:1996) - a mandatory tag field, referenced to as a tag; - a mandatory length field indicating a length L; - a conditional value field of L bytes (when L is not equal to 00).
32、3.1.3.4 dictionary a set of headerlists defining the fixed formats used by the IEP 3.1.3.5 headerlist a data element containing a concatenation of tag-length pairs without delimiters 3.1.3.6 primitive data object a data object where the value field shall not be considered a data object 3.1.3.7 a val
33、ue identifying a given data element, either uniquely or in conjunction with one or more other tags tag In order to emphasize terms specific to a general IEP System, throughout this European Standard, these terms commence with capital letters, e.g. Data Object. O BSI 12 1999 I lb2Libb9 0820099 Lib7 P
34、age 7 EN 1546-4:1999 3.2 Symbols and abbrevations A nm ?0?9? and ?A?F? When formats of data elements are described, the following conventions are used: vector (identifier for an ordered set of Data Elements) the range from n to m (inclusive) the sixteen hexadecimal digits. b nx an x ASN. 1 BCD BER D
35、D ?C ,EP LDA LSAM PDA PSAM SAM TEHL TH L TLV TOD binary numeric (BCD) coding of x digits, e.g. n 6 means 6 numerical digits (coded on 3 bytes) alphanumeric coding of x characters (according to IS0 8859-1:1987) abstract syntax notation, one binary coded decimal basic encoding rules discretionary data
36、 integrated circuit Inter-sector electronic purse load device application load SAM purchase device application purchase SAM secure application module tag for an extended headerlist tag for a headerlist tag-length-value tag for operational data 4 Description of the Dictionary mechanism Nhen the derau
37、lt fixed message formats defined in EN 1546-3 are not used, the rules laid out in this part on EN 1546 shall be applied. 4.1 Introduction The use of Dictionaries as defined in this part of EN 1546 is a method for implementing message formats in IEP Systems. It enables other lengths for some Data Ele
38、ments, a different order of Data Elements in messages and the identification of which Discretionary Data elements (and their lengths) are included in the messages. The mechanism is based on TLV coding. The IEP indicates whether TLV coding of Data Elements is required according to the value of the ap
39、plication profile of the IEP (APIEP). The exact details of coding APIEP are given in 4.2. If the IEP supports TLV coding, the Data Elements sent in the messages as defined in EN 1546-3 can have lengths and ordering different from that defined in EN 1546-3. For each transaction type and optionally fo
40、r each logfile, a headerlist shall be defined and may be stored in the IEP. O BSI 12 1999 Page 8 EN 1546-4:1999 Terminals can read the IEPs headerlists whenever necessary using the Get Data command as defined in4.7. The headerlists give all the information necessary to build and interpret the messag
41、es to and from the IEP as tt . consist of a number of Tag-length pairs, defining the presence and the order of each Data Element in a message/log record as well as its length. Data Elements transmitted in the application-specific messages are not tagged, .e. Tag and length fields are not transmitted
42、, but shall conform to the fixed format and order defined in the corresponding headerlist. 4.2 Indication of the use of TLV coding The IEP shall indicate to the terminal equipment whether fixed formats, as defined in EN 1546-3 are used or not. Two bits (b4-b3) in the first byte of the Data Element A
43、PIE are used for this purpose. Normally, the terminal equipment will receive this Data Element as part of the application selection. The following four possible combinations exist for the coding of bits b4-b3 in AEP- - b4-b3 = O O: ASN.1-BER is not used (fixed formats according to EN 1546-3 are used
44、); - b4-b3 = O 1: headerlists for commands and responses are present in the IEP; - b4-b3 = 1 O: headerlists for logfile layouts are present in the IEP (fixed formats are used); - b4-b3 = 1 1: headerlists for commands, responses and logfile layouts are present in the IEP. 4.3 Structure of the headerl
45、ist A headerlist defines the list of Data Elements, their length and in which order they are concatenated in a message. A headerlist is either simple or extended. A simple headerlist comprises: - a Tag-length pair, THL (Tag for a headerlist), which identifies the headerlist and its length; - an orde
46、red set of Tag-length pairs, TODS (Tags for Operational Data), one for each Data Element of the message. A simple headerlist is a primitive Data Object as defined in ISO/IEC 8825. An extended headerlist comprises: - a Tag-length pair, TEHL, which identifies the headerlist and its length; - a headerl
47、ist (simple or extended). An extended headerlist is a constructed Data Object as defined in ISOAEC 8825. For example, the headerlist of the Purchase transaction specifies the Tag-length pairs for all the cornmandshesponses belonging to this transaction. These are: a) the Tag-length pairs in the Init
48、ialize IEP for Purchase command and response; b) the Tag-length pairs in the Debit IEP for Purchase command and response, first step; c) the Tag-length pairs in the Debit IEP for Purchase command and response, subsequent step; d) the Tag-length pairs in the Debit IEP for Purchase Acknowledgement com
49、mand and response. O BSI 12 1999 Page 9 EN 154641 999 Co Lo Headerlists are coded as shown in Figure 1. Cl Ll c, L2 p3 L3 v3 p4 L4 v4 p5 L5 v5 T, L, Specific T, L, Specific T, L, Specific value value value T2 L, 4 v, . TI LI + Y- T L Figure 1 - Coding of a headerlist Ti Li T, L, . Co, CI, C2 are Tags (T) of Constructed Data Objects with lengths b, LI, L, and values V, VI, V, respectively vhich define subsets of an IEP headerlist and are compatible with ASN.l. L EO OC El OA CA 03 CE 8180 5F24 03 CF 40 For example Co could be the Tag of t
