CMP SE Test Applet Requirements - Home - EMVCo...Command added to the test applet to permit the update of the Application Discretionary Data of an application ... Other editorial changes:

© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV

® is a

registered trademark or trademark of EMVCo, LLC in the United States and other countries.

EMV®

Contactless Mobile Payment Type Approval

CMP SE Test Applet Requirements

Version 1.2.0

February 2017

EMV® Contactless Mobile Payment Type Approval

CMP SE Test Applet Requirements v1.2.0 Page 2


® is a


Legal Notice The EMV® Specifications are provided “AS IS” without warranties of any kind, and

EMVCo neither assumes nor accepts any liability for any errors or omissions contained in these Specifications. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AS TO THESE SPECIFICATIONS.

EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to determine whether any implementation of the EMV® Specifications may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of the EMV® Specifications should consult an intellectual property attorney before any such implementation.

Without limiting the foregoing, the Specifications may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement these Specifications is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for

any party’s infringement of any intellectual property rights in connection with the EMV®

Specifications.




® is a


Revision Log – Version 1.2.0

The following changes have been made to the document since the publication of Version 1.1.0. Some of the numbering and cross references in this version have been updated to reflect changes introduced by the published bulletins. The numbering of existing requirements did not change, unless explicitly stated otherwise.

Incorporated changes described in the following Specification Updates:

Maximum value for N for image A19 is updated from 5 to 4

Minimum Value for N in image A2 is 8

Image A14.1 and A14.2 deleted

Image A25 replaced by a new image created to support the AAUI SB 166 – 2nd edition – section 8. PPSE answer truncation for Internal Mode

Image A27 is created to support the AAUI SB 166 – 2nd edition – section 3. Notification of Priority Changes in Internal Mode

Image A28 is created to support the AAUI SB 166 – 2nd edition – section 3. Notification of Priority Changes in Internal Mode

Command added to the test applet to permit the update of the Application Discretionary Data of an application

Clarification of the post personalization mode

Other editorial changes:

Footer




® is a


Table of Contents

1 About this document ................................................................................................... 5

1.1 Introduction ......................................................................................................... 5

1.2 Reference Documents ........................................................................................ 6

1.3 Glossary of Terms ............................................................................................... 7

2 CMP SE Test Application Configurations .................................................................. 9

2.1 Configuration A1 Details.................................................................................... 12


2.3 Configuration A3.1/ A3.2 Details ....................................................................... 13



2.6 Configuration A12 Details .................................................................................. 15

2.7 Configuration A13.1/A13.2 Details .................................................................... 16










3 Description of the SE CMP Test Applet ................................................................... 25

3.1 Overview ........................................................................................................... 25

3.2 Communication Requirements .......................................................................... 25

3.3 Personalization Requirements........................................................................... 25

3.4 Post Personalization Requirements................................................................... 27

4 CMP SE Test Applet – EMVCo Implementation ....................................................... 30

4.1 Resources ......................................................................................................... 30

4.2 Installation Parameters ..................................................................................... 30




® is a


1 About this document

1.1 Introduction

To support the EMVCo Contactless Mobile Payment Type Approval Process, EMVCo makes available to laboratories and product providers a GP compliant CMP SE Test Applet. The CMP SE test applet emulates a contactless payment application and makes it possible to run the tests for Type Approval. The purpose of this document is to publish the CMP SE test applet requirements allowing third party implementations supporting other mobile product architectures, such as mobile products with a non GP compliant embedded Secure Element. It includes the test profiles definition, the personalization features that have to be supported by the application in order to configure the product under test with the various profiles as well as the commands that will be used during the tests. This document also describes the EMVCo implementation of the CMP test applet. The CAP file is made available for testing of GP compliant embedded Secure Element upon signature of a license agreement with EMVCo . Note: EMVCo makes no guarantee that all EMVCo CMP qualified tools are compatible with such third party implementations. Note: EMVCo does not qualify third party implementations and cannot provide support when test cases or qualified test tools are found to be incompatible with such implementations.




® is a


1.2 Reference Documents

Table 1-1: Reference Documents

Ref. Document Title Version

[AAUI] EMVCo Contactless Mobile Payment – Application Activation User Interface – Overview, Usage Guidelines, and PPSE Requirements

Version 1.0 December 2010

[EMVCo CMP ADMIN]

EMVCo Contactless Mobile Payment Type Approval – Administrative Process

Latest available version

[ICS1] EMVCo Contactless Mobile Payment – Application Activation User Interface Implementation Conformance Statement


[ICS2] EMVCo Contactless Mobile Payment – PPSE Applet Implementation Conformance Statement


[CPS] Common Personalization Specifications V1.1 September 2007

[GPCS] GlobalPlatform, Card Specification Version 2.2.1 January 2011

[GPCS-C] GlobalPlatform Card, Contactless Services Card Specification v2.2 – Amendment C

Version 1.1 April 2013




® is a


1.3 Glossary of Terms

The following abbreviations and notations are used in this document

Table 1-2: Abbreviations

AFI Application Family Identifier

APDU Application Protocol Data Unit

AID Application IDentifier

CLA CLAss

CMP Contactless Mobile Payment

DF Dedicated File

DGI Data Group Identifier

ETSI European Telecommunications Standards Institute

FCI File Control Information

FWI Frame Waiting time Integer

GP Global Platform

HCI Host Controller Interface

ICS Implementation Conformance Statement

INS INStruction

PICC proximity integrated circuit card

PPSE Proximity Payment System Environment

PUPI Pseudo-Unique PICC Identifier, Type B

SE Secure Element

SECM Secure Element Contactless Management

SW Status Word

Application Activation User Interface: A user interface application on a handset that enables the consumer to manage the use of their contactless applications. CMP SE Test Applet – SE applet specified in this document to test the External and Internal Mode. Contactless Interface: the communication interface between a contactless terminal and the PPSE Device Interface: the communication interface between the Mobile (AAUI) and the PPSE External Mode: The mode in which the AAUI provides the PPSE with the details of the active applications that will be presented to a contactless payment terminal. Group: A set of contactless applications consisting of a group head/owner application and one or more member applications. Internal Mode: The mode in which the PPSE itself collects details of the active applications and builds the data to be presented to the contactless payment terminal. Proximity Payment System Environment: mechanism for presenting the contactless applications available for conducting a transaction to a Contactless Payment Terminal. The PPSE is the first application selected by a Contactless Payment Terminal, and based on the information provided by the PPSE, the terminal uses the highest priority application it supports to process a contactless payment.




® is a


Secure Element: A tamper resistant module in a handset capable of hosting applications in a secure manner. A Secure Element may be an integral part of the handset, or may be a removable element which is inserted into the handset for use. Switched On: A state in which the Handset is powered up and the user interface is available for use.




® is a


2 CMP SE Test Application Configurations EMVCo has defined several CMP SE Test Applet Configurations that shall be used by the test cases:

A1: Three CMP SE Test Applets configured for Internal Mode, Mobile Switched On and not activated

A2: Maximum Number of standalone CMP SE Test Applets configured for Internal Mode, Mobile Switched On (applications not activated). Minimum value for the maximum number of standalone CMP SE Test Applets is 8.

A3.1: Two CMP SE Test Applet Group Head with three Contactless Test Payment Applications Members configured for Internal Mode, Mobile Switched On (applications not activated) ; all applications (heads and members are configured to declare the PPSE as its CREL.

A3.2: same as 3.1 but only head applications are configured to declare the PPSE as its CREL

A4: Five standalone CMP SE Test Applets with Base AID set configured for Internal Mode, Mobile Switched On (applications not activated)

A5: Same as A1 but for Mobile not Switched On (Display Required Indicator=’01)


A7.1: Same as A3.1 but for Mobile not Switched On (Display Required Indicator=’01)

A7.2: Same as A3.2 but for Mobile not Switched On (Display Required Indicator=’01)


A9: Same as A1 with Policy restrictions configured for Mobile Switched On (Display Required Indicator=’01)

A10: Same as A1 but for External Mode

A10.1: Same as A10 with AID1 activated on contactless interface

A10.2: Same as A10 with all AIDs activated on contactless interface

A11: Same as A5 but for External Mode

A12: Maximum CMP SE Test Applet Group Head with two Contactless Test Payment Applications Members configured for Internal Mode, Mobile Switched On (applications not activated)

A13.1: Single Test Payment Application Group Head with Maximum Number of Contactless Test Payment Applications Members configured for Internal Mode, Mobile Switched On (applications not activated) ; all applications (heads and members are configured to declare the PPSE as its CREL.

A13.2: same as A13.1 but only head application is configured to declare the PPSE as its CREL..




® is a


A15: Four standalone CMP SE Test Applets with Base AID set configured for Internal Mode, Mobile Switched On, sharing a part of discretionary data (applications not activated)

A16: Three CMP SE Test Applets configured for Internal Mode, Mobile Switched On and not activated, having 2 directory entries in Discretionary data

A17: Three CMP SE Test Applets configured for Internal Mode, Mobile Switched On and not activated, having a directory entry with an AID length shorter that the instantiated AID in Discretionary data

A18: Two CMP SE Test Applets configured for Internal Mode, Mobile Switched On and not activated, having a directory entry with an AID length (longer/different) that the instantiated AID in Discretionary data

A19: up to 4 CMP SE Test Applet Group Head with one Contactless Test Payment Applications Member configured for Internal Mode, Mobile Switched On (applications not activated)

A20: Same as A1 but all applications have Application Family Identifier (AFI) with value '20'

A21: Same as A2 but all applications AIDx with x having odd value have Application Family Identifier (AFI) with value '20'

A22.1: Same as A3.1 but all applications have Application Family Identifier (AFI) with value '20'

A22.2: Same as A3.2 but all applications have Application Family Identifier (AFI) with value '20'

A23: Same as A4 but all applications AIDx with x having odd value have Application Family Identifier (AFI) with value '20'

A24: Same as A15 but all applications have Application Family Identifier (AFI) with value '20'

A25: Eight CMP SE Test Applets configured for Internal Mode, and not activated. Long labels to generate PPSE truncation.

A26: Three CMP SE Test Applet Group Head with three Contactless Test Payment Applications Members configured for Internal Mode, Mobile Switched On (applications not activated) ; all applications (heads and members are configured to declare the PPSE as its CREL.

A27: Seven CMP SE Test Applets configured for Internal Mode, and not activated. Four of the applications configured to work when mobile is not Switched On (Display Required Indicator=’01)

A28: Eight CMP SE Test Applets configured for Internal Mode, and not activated, some with no application AFI, some with Application AFI with value ‘20’, some with Application AFI with value different than ‘20’.




® is a





® is a


2.1 Configuration A1 Details

3 AIDs

AID1= ‘A1111111111010’,

o Application Label= ‘Label1’,

o Kernel ID= ‘01’,

AID2= ‘A2222222221010’,



AID3= ‘A3333333331010’,



o Extended Selection= ‘03’,

o Directory Discretionary Template= ‘1122334455667788’.


N AIDs: N is the Maximum number of AID of Standalone application supported (declared in the ICS). N >=8.

AID1= ‘A0010101011010’,



AID2= ‘A0020202021010’,



….

AIDN= ‘A0NNNN1010’,

o Application Label= ‘LabelN’,

o Kernel ID= ‘N’,




® is a


2.3 Configuration A3.1/ A3.2 Details

2 AIDs that represent Application group heads and 3 AIDs members per group:

AID group head1= ‘A0010101011010’,

o Application Label= ‘LabelH1’,


AID group Member 1 Head1= ‘A0010101011111’,

o Application Label= ‘LabelH1M1’,








AID Group Head2= ‘A0020202021010’,















® is a


For A.3.1, each application (head, member) has a single directory entry in Application Discretionary Data with:

AID

Application Label

Kernel ID

For A.3.2, only head applications have several directory entries in Application Discretionary Data with:

AID, Application Label , Kernel ID for the Head

AID, Application Label , Kernel ID for the Member 1




Five standalone CMP SE Test Applets with Base AID set:

o DF name 1= ‘A0010101011010’, Application Label 1= ‘Label1’, Kernel ID1= ‘01’, Base AID 1= ’05’




o DF name 5= ‘A0010101015010’, Application Label 5= ‘Label5’, Kernel ID5= ‘05’


The Policy restrictions of the configuration are defined below:

DF Name 1 ‘A1111111111010’, cannot be activated when DF Name 2 ‘A2222222221010’ or DF Name 3 ‘A3333333331010’ is activated




® is a



N AIDs that represent Application group heads and 2 AIDs members per group (with N is the Maximum number of groups defined in ICS):

AID group head1= ‘A0010101011010’,









…..

AID Group Head N= ‘A0’ NNNN ’1010’,

o Application Label= ‘LabelH’ N,

o Kernel ID= N,

AID group Member 1 Head N= ‘A0’ NNNN ‘1111’,

o Application Label= ‘LabelH’ N ‘M1’,

o Kernel ID= N,



o Kernel ID= N,

With N is the Maximum number of groups defined in ICS




® is a


2.7 Configuration A13.1/A13.2 Details

One AID that represent the single Application group head and N AIDs members in the group (with N is the Maximum number of members in a group defined in ICS):

AID group head1= ‘A0010101010000’,









….

AID group Member N Head1= ‘A001010101’NN,

o Application Label= ‘LabelH1M’N,


For A.13.1, each application (head, member) has a single directory entry in Application Discretionary Data with:

AID

Application Label

Kernel ID

For A.13.2, only head application has several directory entries in Application Discretionary Data with:

AID, Application Label , Kernel ID for the Head




..

AID, Application Label , Kernel ID for the Member n




® is a



Four standalone CMP SE Test Applets with Base AID set and a part of discretionary data shared:

o DF name 1= ‘A00101010110100001’, Application Label 1= ‘Label1’, Kernel ID1= ‘01’, Base AID 1= ’08’ in the second directory entry of the Application Discretionary Data , (DF name = ‘A0010101011010’, Application Label = ‘Label’, Kernel ID= ‘02’, Base AID 1= ’07’, in the first directory entry of the Application Discretionary Data)

o DF name 2= ‘A00101010110100002’, Application Label 2= ‘Label2’, Kernel ID2= ‘01’, Base AID 2= ’08’, in the second directory entry of the Application Discretionary Data (DF name = ‘A0010101011010’, Application Label = ‘Label’, Kernel ID= ‘02’, Base AID 1= ’07’, in the first directory entry of the Application Discretionary Data)

o DF name 3= ‘A00101010110100101’, Application Label 3= ‘Label3’, Kernel ID3= ‘03’, Base AID 2= ’08’, in the second directory entry of the Application Discretionary Data (DF name = ‘A0010101011010’, Application Label = ‘Label’, Kernel ID= ‘02’, Base AID 1= ’07’, in the first directory entry of the Application Discretionary Data)

o DF name 4= ‘A001010101101002’, Application Label 4= ‘Label4’, Kernel ID4= ‘04’.


Three standalone CMP SE Test Applets with two entries in discretionary data:

o DF name 1= ‘A1111111111010’010203040506070809’, Application Label = ‘Lab1’, Kernel ID= ‘04’, in the second directory entry of the Application Discretionary Data , (DF name = ‘A1111111111010’, Application Label = ‘Label1’, Kernel ID= ‘01’, in the first directory entry of the Application Discretionary Data)

o DF name 2= ‘A222222222101000’, Application Label = ‘Lab2’, Kernel ID= ‘05’, in the second directory entry of the Application Discretionary Data (DF name = ‘A2222222221010’, Application Label = ‘Label2’, Kernel ID= ‘02’, in the first directory entry of the Application Discretionary Data)

o DF name 3= ‘A3333333331010’, Application Label= ‘Label3’, Kernel ID3= ‘03’, in the first directory entry of the Application Discretionary Data (DF name = ‘A333333333’, Application Label = ‘Lab3’, Kernel ID= ‘06’, in the second directory entry of the Application Discretionary Data)




® is a



Three standalone CMP SE Test Applets with the AID length set in the an entry in discretionary data shorter that the instantiated AID:

o DF name 1 (instantiated)= ‘A1111111111010010203040506070809’, (DF name = ‘A1111111111010’, Application Label = ‘Label1’, Kernel ID= ‘01’, in the directory entry of the Application Discretionary Data)

o DF name 2 (instantiated)= = ‘A222222222101000’ (DF name = ‘A2222222221010’, Application Label = ‘Label2’, Kernel ID= ‘02’, in the directory entry of the Application Discretionary Data)

o DF name 3 (instantiated)= = ‘A3333333331010’, (DF name = ‘A333333333’, Application Label = ‘Label3’, Kernel ID= ‘03’, in the directory entry of the Application Discretionary Data)


Two standalone CMP SE Test Applets with the AID longer/different than the instantiated set in the entries in discretionary data:

o DF name 1 (instantiated)= ‘A1111111111010’, (DF name = ‘A9999999999090’, Application Label = ‘Label1’, Kernel ID= ‘01’, in the directory entry of the Application Discretionary Data)

o DF name 2 (instantiated)= = ‘A2222222221010’ (DF name = ‘A22222222210100102030405’, Application Label = ‘Label2’, Kernel ID= ‘02’, in the directory entry of the Application Discretionary Data)


N AIDs that represent Application group heads and 1 AIDs members per group (with N is the Maximum number of groups defined in ICS with a maximum value of 4):

AID group head1= ‘A0010101011010’,






…..




® is a


AID Group Head N= ‘A0’ NNNN ’1010’,

o Application Label= ‘LabelH’ N,

o Kernel ID= N,



o Kernel ID= N,

With N is the Maximum number of groups defined in ICS (value of N=4 should be used if the maximum number of groups in ICS is more than 4)


8 AIDs

AID1= ‘A1111111111010’,

o Application Label= ‘ApplicationLabe1’,


AID2= ‘A2222222221010’,



AID3= ‘A3333333331010’,



AID4= ‘A4444444441010’,



AID1= ‘A5555555551010’,



AID6= ‘A6666666661010’,






® is a


AID7= ‘A7777777771010’,



AID8= ‘A8888888881010’,




3 AIDs that represent Application group heads and 3 AIDs members per group:

AID group head1= ‘A0010101011010’,

o Application Label= ‘Application H1’,



o Application Label= ‘Application H1M1’,








AID Group Head2= ‘A0020202021010’,









® is a








AID Group Head3= ‘A0030303031010’,












each application (head, member) has a single directory entry in Application Discretionary Data with:

DF Name (AID)

Application Label

Kernel ID


7 AIDs

AID1= ‘A0010101011010’,






® is a


o Display Required Indicator=’01

AID2= ‘A0020202021010’,




AID3= ‘A0030303031010’,




AID4= ‘A0040404041010’,




AID5= ‘A0050505051010’,




AID6= ‘A0060606061010’,




AID7= ‘A0070707071010’,





8 AIDs




® is a


AID1= ‘A0010101011010’,



o No AFI

AID2= ‘A0020202021010’,



o AFI = ‘20’

AID3= ‘A0030303031010’,



o No AFI

AID4= ‘A0040404041010’,



o AFI = ‘20’

AID5= ‘A0050505051010’,



o No AFI

AID6= ‘A0060606061010’,

o AFI = ‘10’

AID7= ‘A0070707071010’,

o AFI = ‘30’

AID8= ‘A0080808081010’,

o AFI = ‘80’




® is a





® is a


3 Description of the SE CMP Test Applet

3.1 Overview

There are two functional objectives for this test application:

In External Mode, the CMP SE Test Application shall be able to activate itself (by a command or at personalization) or via the SECM, independently of the PPSE update. When activated, the CMP SE Test Applet shall be able to respond to the Select AID command.

In Internal Mode, the CMP SE Test Application shall be able to activate itself or via the SECM, with an automatic update of the PPSE. When activated, the CMP SE Test Applet shall be able to respond to the Select AID command.

Several instances of the CMP SE Test Applets can be created, each instance has its own personalization data and its own State.

3.2 Communication Requirements

Supplementary logical channels and the logical channels numbers 1 to 19 shall be supported by the CMP SE Test Applet are parameters declared in [ICS1] or [ICS2].

3.3 Personalization Requirements

3.3.1 Personalization Commands The personalization commands interface defined in [CPS] shall be supported:

SELECT AID

INITIALIZE FOR UPDATE

EXTERNAL AUTHENTICATE

STORE DATA

Establishment of a secure channel is required before starting the personalization of the CMP SE Test Applet. The level of security of the secure channel can be no secure messaging (Authentication only), Mac, or Mac and encryption For Secure Elements compliant with [GPCS-C], the CMP SE Test Applet shall implement [AAUI] Annex A.1.1 which specifies the structure of the Payment Application – CRS Contactless data, and also specifies the GlobalPlatform API to be used during personalization of the SE Test Application




® is a


3.3.2 Store Data The command Store Data has been defined to specify the data object needed to populate the CRS during the application personalization. The DGIs defined below shall be supported:

Table 3-1: DGIs supported in Store Data command

Data object CRS Tag value

DGI Presence for Internal Mode

Presence for External Mode

FCI ‘9102’ Mandatory Mandatory

Application Discretionary Data

‘A6’ ‘4000’ Mandatory Optional

Application Group Head ‘A2’ ‘4001’ Conditional Conditional

Application Group ‘A3’ ‘4002’ Conditional Conditional

Display Required Indicator ‘88’ ‘4003’ Optional Optional

Application Family Identifier

‘87’ ‘4004’ Optional Optional

Application Image Template

‘6D’ ‘4005’ Optional Optional

URI ‘5F50’ ‘4006’ Optional Optional

Display Message ‘5F45’ ‘4007’ Optional Optional

Policy Restricted Applications

‘A5’ ‘4008’ Optional Optional

Activation ‘4009’ Mandatory Mandatory

CREL Application AID ‘A4’ ‘400A’ Conditional Not present

The DGI ‘9102’ contains the template ‘A5’ (tag, length and value), of the FCI according to [CPS]; the CMP SE test applet shall build the FCI (template’ 6F’) with a concatenation of its AID (tag ‘84’) and template ‘A5’ .

The DGIs ‘4000’ – ‘400A’ contains the value field of the respective CRS tag value indicated in Table 3-1. For Secure Elements compliant with [GPCS-C], the CMP SE Test Applet must populate the CRS using its GPCLRegistryEntry as described in [AAUI] Annex A.1.1.1. Refer to [GPCS-C] for the formatting of the CRS tag values.

When the Application Group/Application Member is supported by the SECM; If a CMP SE test applet instance is intended to be a member of a group, the CRS tag ‘A2’ value (DGI ‘4001’) shall be present, If this CMP SE test applet instance is a group head, the CRS tag ‘A3’ value (DGI ‘4002’) is optional.

If the DGI ‘4003 (Display Required Indicator) is set to ‘00’ or is not present, it indicates that the CMP SE test applet requires Mobile switched on in Internal Mode. The DGI is not significant in External Mode.

The DGI ‘400A’ ( CREL Application AID List) contains the tag ‘A4’ value. When Internal Mode is selected, the CREL Application AID List shall be personalized with the AID of the PPSE ('325041592E5359532E4444463031') . When External Mode is selected, the CREL Application AID List shall not be personalized.

The DGI ‘4009’ Activation indicates the Status ‘Deactivated’ with a value ‘00’ and the Status ‘Activated’ with a value ‘01’.




® is a


For External Mode, the DGIs ‘4000’ – ‘4009’ may be not personalized if the CMP SE test applet instance has not the self-activation privilege (in this case, the CMP SE test applet instance can only be activated by the SECM).

The Store Data Command of the CMP SE Test Applet shall be coded as follows

Table 3-2: Store Data Command Format for the Test Application

Code Value

CLA ‘8x’

INS ‘E2’

P1 ‘00’ or ‘80’ (for the Last Store Data command)

P2 ‘00’

Lc Var.

Data

The Data field shall contain a single DGI defined in Table 1.

The maximum DGI length to be supported is 240 bytes.

The command shall be rejected with SW=’6A80’ when not correctly formatted (DGI not known, DGI length not consistent).

When P1=’80’ (last Store Data), the command shall be rejected with SW=’6885’ if the Application FCI (DGI ‘9102’) and Activation (DGI ‘4009’) are not personalized.

The application switches to post personalization mode when the last Store Data has been received and processed successfully

3.4 Post Personalization Requirements

Two commands shall be supported after personalization is completed:

SELECT AID to select the CMP SE Test Applet .

SET STATUS to set the CMP SE Test Applet State (Activated/Deactivated) or to Assign or Reset Override Priority.

STORE DATA to modify the Application Discretionary Data (Tag ‘A6’) of an application

3.4.1 Select AID The command shall be supported for an AID length in the range [5,16]. EMV book 1 command structure shall be supported. There is no requirement about the Select response except a Status Word 9000 when selection is done on Device Interface. The FCI compliant EMV Book 1 shall be returned in Select response when Selection is performed on Antenna Interface




® is a


3.4.2 Set Status The command Set Status has been defined to specify the State (in External or Internal Mode) or to override the Priority of the CMP SE Test Applet (in Internal Mode only). Two States have been defined:

Activated

Deactivated.

The command Set Status is supported only when the CMP SE Test Applet is personalized. The Set Status Command of the CMP SE Test Applet shall be coded as follows

Table 3-3: Set Status Command Format for the Test Application

Code Value

CLA ‘8x’

INS ‘F0’

P1 See below

P2 See below

Le ‘00’

The P1 parameter shall be coded as follows

Table 3-4: Set Status – Parameter P1

Value Meaning

‘01’ Availability State

‘02’ Assign or Reset Override Priority

The P2 parameter shall be coded as follows when P1=’01’ (Availability State)

Table 3-5: Set Status – Parameter P2 – Availability State

Value Meaning

‘01’ CMP SE Test Applet to be set to ‘Activated’

‘00’ CMP SE Test Applet to be set to ‘Deactivated’

The P2 parameter shall be coded as follows when P1=’02’ (Assign or Reset Override Priority)

Table 3-6: Set Status – Parameter P2 – Override Priority

Value Meaning

‘02’ Assign Override Priority

‘82’ Reset Override Priority




® is a


For Secure Elements compliant with [GPCS-C]:

When P1=’01’ (CMP SE Test Applet to be set to ‘Activated’/‘Deactivated’), the CMP SE Test Applet shall inform the SECM (CRS) about the application status using the setCLState() method.

When P1=’02’ (Assign/Reset Override Priority Test Application), the CMP SE Test Applet shall inform the SECM (CRS) about the application priority using the setVolatilePriority() method.

The command Set Status shall be rejected with SW=’6985’ when the CMP SE Test Applet is not personalized. The command Set Status shall be rejected with SW=’6984’ when the CMP SE Test Applet has not been activated due to a conflict or any other issue. Command Data The command data is empty. Response Data No response data is returned by the Set Status command.

3.4.3 Store Data The command Store Data supports the update of the DGI 4000 (value of the Application Discretionary Data - Tag ‘A6’- of an instance of the CMP SE Test Applet), when the CMP SE Test Applet is personalized. Only this DGI is supported post personalization. Upon reception of the command, the application shall transmit the Application Discretionary Data to the SECM. Note: post personalization is not supported within a secure channel. Consequently the command shall be sent with CLA = 80 and Initialize Update/External Authenticate sequence is not required.




® is a


4 CMP SE Test Applet – EMVCo Implementation

This section applies to the EMVCo implementation of the CMP SE Test application for Secure Elements compliant with [GPCS-C]:

4.1 Resources

The CMP SE test applet required resources are defined below:

Table 4-1: EMVCo CMP SE Test Applet Size

CMP SE test applet EEPROM Size RAM Size

Code size in the card 2.3 k

Installation application 0.2k 20 bytes

4.2 Installation Parameters

No specific install parameter for the functional part is required for this applet. It is required to set the contactless communication parameters at CMP SE test applet installation if no default parameters are set in the platform. All these setting shall done according to [GPCS-C]. In order for the CMP SE Test Applet to set its own state, it must be installed with the Contactless Self-Activation privilege as defined in [GPCS-C].

Note : During the installation of the CMP SE test applet, it is possible to set the CRS Tag values described in the Table 3-1 (except DGI 9102 content), using the applet Global Platform installation parameters. Refer to [GPCS-C] user Interaction Parameters section and Contactless Protocol parameters Structure section to personalize the CMP SE test applet during its installation (instead of running the personalization sequence described in section 3.3). Personalization of CRS Tag values during the installation phase may require the usage of Install for Registry Update APDU command due to the length of the data to send. The values of the GlobalPlatform tags used to configure the user Interaction parameters during the applet installation are not the same as the one described in the Table 3-1 (GlobalPlatform tags for contactless registry data)