PCI Watch

Tracking changes across the Payment Card Industry

SB nº 119: Clarifies Group Member CREL & FCI contactless characteristic declarations, clarifies length of Base AID (Spec Change)

v2.0 Specification Bulletins
Mobile NFC Consumer Device

Specification Bulletin No. 119 Second Edition August 2014 Clarifies Group Member CREL and FCI contactless characteristic declarations, clarifies behavior related to Length of Base AID and corrects the content of the returned PPSE version This Specification Bulletin:

  • Clarifies an ambiguity related to Group Member declarations of the PPSE as a CREL and an FCI for the PPSE in its contactless characteristics
  • Clarifies the behavior related to building an FCI template when a Length of Base AID field is present in a Directory Entry
  • Corrects the content of the version field returned in response to a SELECT command Note: the 2nd edition enhances Part 1 (Group Member Declarations):
  • Issuers are given more flexibility for Group Member Declarations, enabling a better control of the relative application priorities within the group
  • It clarifies the method used by the PPSE application to allocate the Application Priority Indicator for each Directory Entry

Effective Date

This bulletin is effective from Oct 2012 and all CMP type approval related testing will comply with the Specification Bulletin as opposed to the currently published version 1.0 of the Application Activation User Interface document.

Applicability

This Specification Bulletin applies to:

  • EMVCo Contactless Mobile Payment – Application Activation User Interface – Version 1.0 – December 2010

Related Documents

The CMP type approval Level 2 test cases will comply with the final Specification Bulletin.

http://www.emvco.com/

1. Group Member Declarations

Description

The issuer of a CMP application group may choose between two possible configurations:

  • Each CMP application in the group, whether head or member, a member of a group or not, should be is configured to declare the PPSE as its CREL as well as defining FCI data in its Application Discretionary Data containing its own Directory Entry one or more Directory Entries.
  • Or, within the group, only the Head is configured to declare the PPSE as its CREL. In its Application Discretionary Data, the Head defines several Directory Entries: for itself as well as for the other group Members. In this model, group Members do not have the PPSE as CREL and do not define any Application Discretionary Data. In the case of multiple groups, each with multiple Directory Entries, the PPSE configured in Internal Mode shall allocate Priority TLV for each application by respecting both:
  • the “global” priority assigned by the consumer to the application group from the AAUI
  • the relative priority assigned by the Issuer for each application within the group, as it may be defined by the order of Directory Entries in the Application Discretionary Data of the Head application These clarifications affects the following in the AAUI document:
  • , Table A.1, row 19, description cell – Content changes to: “CREL Application AID List – This list identifies the PPSE and other CREL applications, if any.”
  • , section A.1.2.2, 1st bullet of the Notes for the Application Discretionary Data – This bullet changes to: “An application that indicates the PPSE as its CREL has at least one Directory Entry in the data object. It may indicate subsequent Directory Entries - typically, if an issuer chooses to configure its application group so that only the Head application declares the PPSE as its CREL, the group Head should provide its own Directory Entry as well as the Directory Entry (or Entries) of the relevant group Members.”
  • , section A.1.3, 1st sentence of the 3rd paragraph of the 1st bullet of the Behavior – This bullet changes to: “The PPSE retrieves the Directory Entry (or Entries) information of each application for which it is a CREL from the INFO_DISCRETIONARY_DATA of the target GPCLRegistryEntry. GPCLRegistryEntry objects must be considered in the order as returned by method getNextGPCLRegistryEntry()so as to take into account the application prioritization defined by the consumer. For each retrieved Directory Entry of each retrieved GPCLRegistryEntry, the PPSE removes the Length of Base AID TLV (if any) and includes a Priority TLV. If there are multiple Directory Entries, the first entry from the first GPCLRegistryEntry is given the highest priority '01', and each successive entry (first from the same GPCLRegistryEntry if any, then from the subsequent ones if any) is given a continually lesser priority.” http://www.emvco.com/ 2. Base AID Length Behavior Description When building an FCI Template for the PPSE, Directory Entries indicating a Length of Base ID should not affect Directory Entries that do not contain a Length of Base AID, or do not indicate the same Length of Base AID. Therefore any action taken by the AAUI or PPSE should only affect the Directory Entries indicating the Length of Base AID. This affects the following in the AAUI document:
  • , section A.1.2.2, 2nd paragraph of the 2nd bullet of the Notes for the Application Discretionary Data – This paragraph changes to: “For each Directory Entry that contains a Length of Base AID data object, it is the responsibility of the AAUI (External Mode) or the PPSE (Internal Mode), first to check whether any other Directory Entries contain a matching AID. (This match is based on a byte by byte comparison starting from the left most byte of the AID up to the value of the Length of Base AID.) For each match, if the current Directory Entry has a lower priority than the matching Directory Entry, then the current Directory Entry is stripped from the template. Following all matches, if the current Directory Entry is still present in template, the Length of Base AID data object (tag, length and value) is itself stripped from this Directory Entry”
  • , section A.1.2.2, 3nd paragraph of the 2nd bullet of the Notes for the Application Discretionary Data – This paragraph changes to: “The rational for the base AID is that a contactless payment terminal will only interact with the highest priority application even if multiple applications with the same base AID are listed by the PPSE. Therefore, as an optimization of the PPSE, any lower priority application indicating a Length of Base AID, and matching one or more other applications to be listed, can be removed from the list.”
  • , Section A.1.3, 3rd paragraph of the 1st bullet. The following sentence is added to this paragraph: “Refer to section A.1.2.2 for a description of the behavior of the PPSE related to the Length of Base AID field in the case that there are one or more active applications with matching AIDs” 3. PPSE Version Description The version of the PPSE, as described in the current version, is currently coded on a single byte. The coding of the version should actually be coded on 2 bytes. This affects the following in the AAUI document: , Table B.10, row 4, cell 3. The content of this cell changes from”′10′ - Version” to “′3130′ Version”. http://www.emvco.com/