Contactless Services Card Specification v2.2 - Amendment C

Transcription

1 GlbalPlatfrm Card Cntactless Services Card Specificatin v2.2 - Amendment C Versin 1.0 Public Release February 2010 Dcument Reference: GPC_SPE_025 Recipients f this dcument are invited t submit, with their cmments, ntificatin f any relevant patent rights r ther intellectual prperty rights f which they may be aware which might be infringed by the implementatin f the specificatin set frth in this dcument, and t prvide supprting dcumentatin. The technlgy prvided r described herein is subject t updates, revisins, and extensins by GlbalPlatfrm. Use f this infrmatin is gverned by the GlbalPlatfrm license agreement and any use incnsistent with that agreement is strictly

2 2/77 Card Specificatin v2.2 - Amendment C - Cntactless Services Table f Cntents 1. INTRODUCTION SCOPE USE CASES AND REQUIREMENTS NORMATIVE REFERENCES TERMINOLOGY AND DEFINITIONS ABBREVIATIONS AND NOTATIONS REVISION HISTORY SYSTEM OVERVIEW HIGH LEVEL ARCHITECTURE CONTACTLESS REGISTRY SERVICE (CRS) HIGH-LEVEL COMMUNICATION FLOWS Ppulatin and Update f Cntactless Registry Parameters User Interactin TAG ENCODING RULE USER INTERACTION MANAGEMENT DEFINITION AND SCOPE DISPLAY CONTROL INFORMATION POLICY RESTRICTED APPLICATIONS APPLICATION DISCRETIONARY DATA APPLICATION FAMILY DISPLAY REQUIRED INDICATOR APPLICATION GROUPS Definitin and Scpe Head Applicatin Member Applicatins Jining r Leaving an Applicatin Grup Add t the Grup Authrizatin List Remve frm the Grup Authrizatin List CREL APPLICATION Definitin and Scpe CREL Applicatin Registratin Add t the CREL List Remve frm the CREL List CRS APPLICATION Definitin and Scpe NOTIFICATION RULES General Rules CREL Ntificatin CRS Ntificatin Applicatin Ntificatins GLOBALPLATFORM CRS APPLICATION Definitin and Scpe TLV fr User Interactin Parameters Applicatin AID Applicatin Lifecycle State Update Cunters Selectin Pririty Applicatin Grup CREL Applicatin AID List GET STATUS Cmmand

3 Card Specificatin v2.2 - Amendment C - Cntactless Services 3/ Definitin and Scpe Cmmand Message Respnse Message SET STATUS Cmmand Definitin and Scpe Cmmand Message Respnse Message SELECT Cmmand Definitin and Scpe Respnse Message GET DATA Cmmand Definitin and Scpe Cmmand Message Respnse Message CONTACTLESS PROTOCOL MANAGEMENT OVERVIEW AND SCOPE THE OPEN REQUIREMENTS CONTACTLESS PROTOCOL PARAMETERS CURRENT PROTOCOL PARAMETER COMPUTATION Current Prtcl Parameter Initializatin Current Prtcl Parameter: Cmputatin n Activatin Current Prtcl Parameter: Full Cmputatin CONFLICT DETECTION PROCEDURE PROTOCOL PARAMETERS FOR TYPE A (CARD EMULATION MODE) PROTOCOL PARAMETERS FOR TYPE B (CARD EMULATION MODE) PROTOCOL PARAMETERS FOR TYPE F CONTACTLESS PROTOCOL PARAMETERS PROFILES COMMUNICATION INTERFACE ACCESS CONFIGURATION INTRODUCTION, OVERVIEW AND RATIONALE COMMUNICATION INTERFACE ACCESS PARAMETERS SECURITY DOMAIN SETTINGS APPLICATION INSTANCE SETTINGS RULES FOR EXTRADITION APPLICATION SELECTION RESET SCENARIOS WITH MULTIPLE ACTIVE INTERFACES APPLICATION SELECTION PRIORITY GlbalPlatfrm Registry Order Vlatile Pririty ver the Cntactless Interface EXPLICIT AND IMPLICIT SELECTION OVER THE CONTACTLESS INTERFACE CONTINUOUS PROCESSING RECOGNITION ALGORITHM ASSIGNED PROTOCOLS FOR IMPLICIT SELECTION CONTACTLESS PRIVILEGE CONTACTLESS ACTIVATION PRIVILEGE CONTACTLESS SELF-ACTIVATION PRIVILEGE PRIVILEGE CODING APPLICATION AVAILABILITY ON THE CONTACTLESS INTERFACE CONTACTLESS ACTIVATION STATE INITIAL CONTACTLESS ACTIVATION STATE CONTACTLESS INTERFACE AVAILABILITY... 56

4 4/77 Card Specificatin v2.2 - Amendment C - Cntactless Services 9. CUMULATIVE GRANTED MEMORY CUMULATIVE DELETE DEFINITION AND SCOPE SECURITY DOMAIN WITH GLOBAL DELETE PRIVILEGE SECURITY DOMAIN HIERARCHY REMOVAL LOGICALLY DELETED WITH REFERENCES SECURITY DOMAIN APDU COMMANDS LIFE CYCLE STATE CODING INSTALL COMMAND Cntactless Prtcl Parameters Structure Cntactless Prtcl Parameters Prfile Structure User Interactin Parameters Structure Prcessing State returned in the Respnse Message DELETE COMMAND GET STATUS COMMAND Filter Criterin: Tag List ('5C') Respnse Message TOKEN IDENTIFIER BLACKLIST FOR DELEGATED MANAGEMENT DEFINITION AND SCOPE BLACKLIST / REHABILITATE USING STORE DATA COMMAND ADD TO BLACKLIST REMOVE FROM BLACKLIST READ BLACKLIST PROCESSING STATE RETURNED IN THE RESPONSE MESSAGE A. CRS JAVA CARD API B. CONTACTLESS PROTOCOL MANAGEMENT: EXAMPLE B.1. CURRENT PROTOCOL PARAMETERS FOR TYPE A COMPUTATION B.1.1. Value Definitin B.1.2. Prtcl Data Cmputatin: Intermediate Result [A] B.1.3. Prtcl Data Cmputatin: Intermediate Result [B] B.1.4. Prtcl Data Cmputatin: Intermediate Result [C] B.1.5. Current Prtcl Parameter f Type A: Result B.2. PROTOCOL PARAMETER FOR TYPE A: CONFLICT DETECTION B.2.1. Value Definitin... 74

5 Card Specificatin v2.2 - Amendment C - Cntactless Services 5/77 1. Intrductin 1.1. Scpe This dcument defines an extensin f the GlbalPlatfrm Card Specificatin v2.2 [0] t facilitate deplyment f cntactless services in a Secure Element lcated in a mbile handset. Mre specifically, this specificatin defines mechanisms, parameters, and interfaces t set-up and maintain the cnfiguratin f applicatins and cntrl their access t system resurces like cmmunicatin interfaces and memry. GlbalPlatfrm cnfiguratin(s) may require sme r all f the capabilities specified in this dcument. Applicatins that are cnfigured t be usable n a cntactless interface (using mechanisms defined in sectin 5: Cmmunicatin Interface Access Cnfiguratin) are referred t as "Cntactless Applicatins". The term "cntactless" is used thrughut this dcument and references primarily "prximity" technlgies, e.g. ISO/IEC Hwever, it may be pssible that the mechanisms defined in this specificatin are useful t manage access t Applicatins ver a variety f technlgies, such as Bluetth, WiFi, and ISO/IEC Therefre, the term "cntactless" shall nt be understd as a limitatin t strictly "prximity" technlgies. Certain applicatin prviders may chse t limit the accessibility f their Applicatin(s) t specific technlgies, and therefre, may define prfiles specifying these industry-specific limitatins. Althugh the requirements mtivating this Amendment riginated frm a mbile/cntactless services perspective, sme f the cncepts specified in this Amendment are easily applicable beynd this cre use case. This dcument fcuses n parameters and mechanisms required fr Applicatins in card emulatin mde. Applicatins in reader r peer-t-peer mde are beynd the scpe f the current versin f this specificatin Use Cases and Requirements The fllwing requirements shall be cnsidered: The end-user shall be able t: View and priritize the list f services (implemented by a Standalne Applicatin r an Applicatin Grup) based n a user-friendly service management applicatin lcated in r utside f the secure element Activate and deactivate cntactless services (s that a cntactless reader is able/unable t select a specific service) Enable and disable cmmunicatin ver the cntactless interface The Applicatin prvider shall be able t: Prvide technical meta-data (e.g. parameters fr the cntactless prtcl) t clearly define the cntactless envirnment f the Applicatin Prvide end-user selectin meta-data (e.g. lg, family ) t help the end-user t chse the intended service fr activatin, deactivatin, etc. Additinally it shall be pssible t: Grant a Security Dmain a specific amunt f memry resurces. All Applicatins and sub-security Dmains (if present) which are managed by this Security Dmain shall nt be allwed t cnsume mre memry Delete a rt Security Dmain and its hierarchy in a single peratin

6 6/77 Card Specificatin v2.2 - Amendment C - Cntactless Services Prhibit the use f a specific tken n a Security Dmain with the Tken Verificatin Privilege This specificatin is structured accrding t the fllwing tpics: Extensins f the OPEN and the GlbalPlatfrm Registry Applicatin Grups Cntactless Activatin states Management f Cmmunicatin Channel Access Plicy Applicatin Selectin CRS Applicatin and CREL Applicatin Cnflicts between applicatins due t incmpatible cntactless parameters Privileges relative t Cntactless Activatin Memry resurce management within a Security Dmain Hierarchy Deletin f a Security Dmain Hierarchy API fr access t the extended GlbalPlatfrm registry API fr interactins with CRS Applicatin and CREL Applicatin API extensin t the SecureChannel interface enabling an Applicatin t use the secure channel prtcl when the APDU bject is nt available Tken Identifier Blacklist fr Delegated Management 1.3. Nrmative References Standard / Specificatin Descriptin Ref GlbalPlatfrm Card GlbalPlatfrm Card Specificatin v2.2 Specificatin v 2.2 [0] ISO/IEC Identificatin cards -- Cntactless integrated circuit(s) cards -- Prximity cards -- Part 3: Initializatin and anti-cllisin [1] ISO/IEC Identificatin cards -- Cntactless integrated circuit cards -- Prximity cards -- Part 4: Transmissin prtcl [2] ETSI TS Smart Cards; UICC - Cntactless Frnt-end (CLF) Interface; Hst Cntrller Interface (HCI) (Release 7) [3] ISO/IEC Identificatin cards Interindustry data elements fr interchange [4] ISO/IEC Infrmatin technlgy ASN.1 encding rules: Specificatin f Basic Encding Rules (BER), Cannical Encding Rules (CER) and Distinguished Encding Rules (DER) [5] ISO/IEC Infrmatin technlgy 8-bit single-byte cded graphic character sets Part 1: Latin alphabet N.1 [6] IETF RFC 3629 UTF-8, a transfrmatin frmat f ISO [7] ISO/IEC Infrmatin technlgy Telecmmunicatins and infrmatin exchange between systems Near Field Cmmunicatin [8] Interface and Prtcl (NFCIP-1) ETSI TS Smart Cards; Card Applicatin Tlkit (CAT) [9] Java Card 3.0 Runtime Envirnment, Classic Editin Runtime Envirnment Specificatin Java Card Platfrm 3.0, Classic Editin [10] ISO/IEC Infrmatin technlgy Digital cmpressin and cding f cntinuus-tne still images: Requirements and guidelines [11] Table 1-1: Nrmative References

7 Card Specificatin v2.2 - Amendment C - Cntactless Services 7/ Terminlgy and Definitins Table 1-2 defines the expressins used within this Specificatin that use an upper case first letter in each wrd f the expressin. Expressins within this dcument that use a lwer case first letter in each wrd take the cmmn sense meaning. (Tagged data elements are als given an upper case first letter in each wrd f their names.) Term Secure Element Cntactless Applicatin Cntactless Sessin Definitin A Secure Element (SE) is a cmpnent in a device prviding the security and cnfidentiality required t supprt varius business mdels. A SE can exist in any frm factr such as UICC, Embedded SE, memry card, etc. Applicatins that are explicitly r implicitly cnfigured t be usable n a cntactless interface (e.g. ISO based) are referred t as "Cntactless Applicatins". A cntactless sessin starts when the card enters the RF field and ends when the card leaves the RF field. Table 1-2: Terminlgy and Definitins 1.5. Abbreviatins and Ntatins Abbreviatin AID AFI APDU API APSD BER-TLV CL CLF CRS CREL EMV GUI HCI IF ISD MIDP MMI NFC OCE OPEN Meaning Applicatin Identifier. Applicatin Family Indicatr Applicatin Prtcl Data Unit Applicatin Prgramming Interface Security Dmain f the Applicatin Prvider Basic Encding Rules - Tag, Length, Value Cntactless Cntactless Frnt-end interface Cntactless Registry Services Cntactless Registry Event Listener EurPay MasterCard Visa Graphical User Interface Hst Cntrller Interface Interface Security Dmain f the Issuer Mbile Infrmatin Device Prfile Man-Machine Interface Near Field Cmmunicatin Off-Card Entity GlbalPlatfrm Envirnment

8 8/77 Card Specificatin v2.2 - Amendment C - Cntactless Services Abbreviatin P2P PCD PICC PPSE RF SWP TLV URI Meaning Peer t Peer Prximity Cupling Device Prximity Integrated Circuit Card Prximity Payment System Envirnment Radi frequency Single Wire Prtcl Tag, Length, Value Unifrm Resurce Identifier Table 1-3: Abbreviatins and Ntatins 1.6. Revisin Histry 1.0 Initial Release

9 Card Specificatin v2.2 - Amendment C - Cntactless Services 9/77 2. System Overview 2.1. High Level Architecture Figure 2-1 prvides a high level verview f the system architecture relevant t cntactless services specified in this dcument. Card ISD APSD Applicatin Grup App Head App App CRS App CREL App App RTE CRS API CRS (OPEN Extensin) CL Registry Reader Management Peer-t- Peer Mgt. IF [e.g. ISO7816] Handset CRS GUI IF [e.g. SWP] CLF CL IF CL IF CL reader Figure 2-1: High Level Architecture Overview Sme entities shwn in the figure abve are utside the scpe f this dcument but are presented in the figure fr a better understanding f the system cntext. Specifically, the APIs fr Reader Mde, P2P mde, and the realizatin f the lw level cntactless cnnectin between the card and the cntactless terminal, (e.g. direct antenna cnnectin, SWP, r ther), are beynd the scpe f this specificatin. ISD The Issuer Security Dmain (ISD) is the primary, mandatry, n-card cmpnent representative f the Card Administratr, typically the Card Issuer; cf. GP22 [0] APSD The Applicatin Prvider Security Dmain (APSD) is an ptinal n-card cmpnent representative f an Applicatin Prvider.

10 10/77 Card Specificatin v2.2 - Amendment C - Cntactless Services OPEN This entity represents the GlbalPlatfrm Envirnment (OPEN). It prvides an API t applicatins, cmmand dispatch, Applicatin selectin, (ptinal) lgical channel management, and Card Cntent management (see GP22 [0]). CL Registry The Cntactless Registry adds functins t the GlbalPlatfrm Registry Services fr managing Cntactless Applicatins (see sectin 2.2). Applicatin An Applicatin is an executable cmpnent prviding end-user services after having been installed and made selectable by GlbalPlatfrm card management functins. Applicatin Grup An Applicatin Grup is a cncept which allws grup member Applicatins t be represented t the enduser by a dedicated grup Head Applicatin (see sectin 3.3). Head Applicatin The Head Applicatin (see sectin 3.3) is a Cntactless Applicatin which wns the visibility parameters and the Cntactless Prtcl Parameters f an Applicatin Grup. CRS (OPEN Extensin) The Cntactless Registry Service (CRS) is an extensin f the OPEN t manage and prvide access t cntactless registry parameters (see sectin 2.2). CRS Applicatin The CRS Applicatin is an ptinal cmpnent designed fr the management f Cntactless Applicatins by the end user (see sectin 3.9). CREL Applicatin A Cntactless Registry Event Listener (CREL) Applicatin is an Applicatin interested in being ntified f the changes ccurring t ne r mre Cntactless Applicatin (see sectin 3.8). CRS GUI This handset-side cmpnent allws the end-user t interact with the n-card CRS Applicatin. CL Reader The Cntactless Reader represents the card external cntactless cmmunicatin interface allwing ncard and ff-card Cntactless Applicatins t interact with each ther.

11 Card Specificatin v2.2 - Amendment C - Cntactless Services 11/ Cntactless Registry Service (CRS) The Cntactless Registry Service (CRS) is an extensin f the OPEN prviding: The Cntactless Registry; an extensin f the GlbalPlatfrm Registry The CRS API; an extensin f the GlbalPlatfrm API Services fr: Maintaining the Cntactless Registry subsequent t the installatin, update, r deletin f an Applicatin Maintaining the Cntactless Registry subsequent t the activatin, deactivatin, r a change f pririty f an Applicatin Prviding the Cntactless Registry infrmatin upn request frm an authrized entity Ntifying Applicatins f changes made in the Cntactless Registry Cntactless prtcl management Access cntrl n Cmmunicatin Interfaces Applicatin selectin rules n the cntactless interface Cntactless privileges 2.3. High-Level Cmmunicatin Flws This sectin prvides a high level verview f the main cmmunicatin flws between the new system entities intrduced in this specificatin. The flws described belw shw the interactin f the entities when executing the fllwing new functins: Ppulating cntactless registry parameters during Applicatin installatin Ppulating cntactless registry parameters during Applicatin persnalisatin Remving cntactless registry parameters during Applicatin deletin Activatin and deactivatin f Cntactless Applicatins (including cnflict reslutin)

12 12/77 Card Specificatin v2.2 - Amendment C - Cntactless Services Ppulatin and Update f Cntactless Registry Parameters Figure 2-2 shws the flw f ppulating the cntactless registry parameters during the installatin f an applicatin. This flw als applies t the update f the cntactless registry parameters using the INSTALL [fr registry update] cmmand. Off-Card On-Card Applicatin Prvider Security Dmain CRS Applicatin CRS Applicatin CREL Applicatin [0-n] 1 INSTALL cmmand 2 INSTALL cmmand Applicatin parameters Cntactless parameters Ntificatin Ntificatin Figure 2-2: Flw f ppulating an Applicatin s Cntactless Registry Parameters during Installatin CRS shall send ntificatins abut updates f the Cntactless Registry t the CRS Applicatin and registered CREL Applicatins. The fllwing steps are highlighted in the figure abve: 1. The Applicatin Prvider supplies its Applicatin with Cntactless Registry Parameters thrugh its Security Dmain using the INSTALL cmmand. 2. The Security Dmain frwards the INSTALL cmmand t the OPEN. 3. The OPEN ppulates the Applicatin-specific Parameters. 4. The OPEN ppulates the Cntactless Registry Parameters. 5. The CRS API ntifies the CRS Applicatin that a change has ccurred in the Registry entry f that Applicatin. 6. The OPEN ntifies CREL Applicatin(s) referenced by the Applicatin.

13 Card Specificatin v2.2 - Amendment C - Cntactless Services 13/77 Figure 2-3 shws the flw f ppulating r updating the cntactless registry parameters f an applicatin thrugh the applicatin itself. Off-Card On-Card Applicatin Prvider Applicatin CRS CRS Applicatin CREL Applicatin [0-n] 1 Cntactless Parameters 2 Cntactless Parameters 3 Ntificatin 4 Ntificatin Figure 2-3: Flw f ppulating an Applicatin s Cntactless Registry Parameters thrugh itself The fllwing steps are highlighted in the figure abve: 1. The Applicatin Prvider supplies its Applicatin with Cntactless Registry Parameters using a prprietary cmmand. 2. The Applicatin updates its Cntactless Registry Parameters using the CRS API. 3. The CRS Applicatin is ntified f the changes that ccurred t the Applicatin. 4. CREL Applicatin(s) referenced by the Applicatin, if any, are ntified f the changes that ccurred t the Applicatin.

14 14/77 Card Specificatin v2.2 - Amendment C - Cntactless Services Figure 2-4 shws the flw f remving the cntactless registry parameters during deletin f an applicatin. Off-Card On-Card Applicatin Prvider Security Dmain CRS Applicatin CRS Applicatin CREL Applicatin [0-n] 1 DELETE cmmand 2 DELETE cmmand 3 4 Uninstall Remve Entry 5 6 Ntificatin Ntificatin Figure 2-4: Flw f remving an Applicatin s Cntactless Registry Parameters during Deletin The fllwing steps are highlighted in the figure abve: 1. An Applicatin Prvider (ff-card) sends the DELETE cmmand t the assciated Security Dmain f the Applicatin which is t be deleted. 2. The addressed Security Dmain delegates the deletin cmmand t the CRS (an extensin f the OPEN) using prprietary interfaces. 3. The CRS/OPEN invkes the "Uninstall" methd f the Applicatin t be deleted as specified in GP22 [0]. 4. The CRS/OPEN remves all entries f the Applicatin which is t be deleted in the GlbalPlatfrm Registry. The OPEN then deletes the data bjects f the Applicatin. 5. The CRS/OPEN sends the ntificatin abut the deletin f the Applicatin t the CRS Applicatin. 6. CREL Applicatin(s) referenced by the Applicatin, if any, are ntified f the deletin f the Applicatin.

15 Card Specificatin v2.2 - Amendment C - Cntactless Services 15/ User Interactin Figure 2-5 shws the flw f the user interactin during activatin, deactivatin r change f pririty f an applicatin. Off-Card On-Card User CRS Applicatin CRS CREL Applicatin [0-n] 1 Cnflict Reslutin 5 Activate / Deactivate Priritize CL Applicatins Cnflict 2 4 CRS Requests Cnflict Update Registry Ntificatin Figure 2-5: Flw f User Interactin The fllwing steps are highlighted in the figure abve: 1. An Off-Card user interface prvides the user with means t activate and deactivate a Cntactless Applicatin and t define the pririty by which they are cnsidered fr selectin thrugh a cntactless reader. 2. The Off-Card entity maps the user request t ne r mre cmmand APDU defined fr the CRS Applicatin and transmits them t this Applicatin. The CRS Applicatin prcesses these cmmands with the help f an On-Card CRS API. 3. If an Applicatin activatin is requested, the CRS Applicatin asks the CRS t check if the request cnflicts with ne (r mre) f the already activated Applicatins. 4. If a cnflict is detected, a crrespnding respnse is returned t the Off-Card entity t infrm the user f the cnflict. 5. The user can reslve the cnflict by restarting at 1) with deactivating the cnflicting applicatin(s) and then repeating the riginal request. 6. T deactivate, activate (withut a cnflict) r change the selectin pririty f an Applicatin, the CRS updates the Registry entry f the respective Applicatin. 7. CREL Applicatins pssibly linked t the mdified Applicatin are ntified abut the registry change by the CRS Tag Encding Rule All TLVs defined in the Amendment C are encded as specified in GP22 [0]. The Identifier ctet is cntext-specific class as described in ISO/IEC [5]. The tag number is in the range [0,30] and is reserved fr GlbalPlatfrm usage unless explicitly specified therwise.

16 16/77 Card Specificatin v2.2 - Amendment C - Cntactless Services 3. User Interactin Management 3.1. Definitin and Scpe This sectin describes the rles and interactin between the entities invlved in prviding infrmatin that supprt the end-user t chse the Applicatins that are t be activated and deactivated and t priritize the activated Applicatins n the cntactless interface. These entities are the CRS Applicatin, Standalne Applicatins, Applicatin Grups, and Cntactless Registry Event Listener (CREL) Applicatins. This sectin als defines parameters that can be used t manage the visibility f Applicatins as seen by ff-card entities. These User Interactin Parameters are accessed by Security Dmains using the INSTALL cmmands as defined in sectin 11.1 r by the GlbalPlatfrm CRS Applicatin using the GET STATUS r SET STATUS cmmands. Similar functinality is als prvided by the CRS API Display Cntrl Infrmatin Display Cntrl Infrmatin is used t manage an ff-card GUI by prviding infrmatin fr a Lg, a URI r any related display infrmatin. The presence f Applicatin Visibility data is ptinal. Applicatin Visibility data shuld be persnalized fr Applicatins t be visible t the end-user. Typically, Head Applicatins and Standalne Applicatins (see sectin 3.7) shuld be persnalized with this parameter. The Applicatin Visibility data shall be embedded with the Display Cntrl Template (tag '7F20') and may include ne r mre f the fllwing data elements: Tag '5F50': Unifrm Resurce Lcatr (see ISO/IEC [4]). The purpse f this URL is ut f scpe f this dcument Tag '6D': Applicatin Image Template (see [4]) Tag '5F44' Applicatin Image Tag '67' Authenticatin Data (ptinal, therwise the Applicatin Image frmat shall be accrding t ISO/IEC [11]) Tag '53' Image Encding Frmat '01' JPG '02' JPG-2000 '03' GIF '04' PNG-8 '05' PNG-24 '06' BMP '07' t '7F' RFU '80' t '8F' Prprietary usage '90' t 'FF' RFU Tag '5F45': Display Message (Data element cntaining a message t display) (see [4]). The fllwing frmats are defined fr the value f the infrmatin t be displayed t the user. A leading single byte identifier, given belw, shall indicate the display message encding frmat: '01' - Frmat ASCII, which includes displayable characters (alphabetic, numerical, and special) and space in the range frm '20' t '7E', cded n ne byte and left-justified. (see ISO/IEC [6])

17 Card Specificatin v2.2 - Amendment C - Cntactless Services 17/77 '02' - Frmat BCD, which includes nly numerical digits, cded n a nibble (4 bits), left justified, and eventually padded n the right with an 'F' nibble if necessary (i.e. if the number f digits is dd) '03' - Frmat HEX, which is equivalent t a transparent mde ("as is") and includes all binary values cded n ne byte '04' - Frmat UTF-8, which is able t represent any character in the UNICODE character set. (see IETF RFC 3629 [7]) 3.3. Plicy Restricted Applicatins The Plicy Restricted Applicatins TLV prvides ne r mre AIDs f Applicatins that shuld nt be ACTIVATED n the cntactless interface at the same time as the Applicatin which has this TLV in its Registry. This TLV is nt used by the OPEN fr cntactless prtcl parameter cnflict reslutin r fr any ther purpse. This TLV may be used by the CRS Applicatin and CREL Applicatins when applying their specific business lgic. Nte: If an Applicatin has the SELF_ACTIVATION privilege, the CRS Applicatin will nt be invlved in the activatin f the Applicatin, althugh the CRS Applicatin will be ntified f this activatin and may take actin based n its wn business lgic and privileges. The table belw defines the value part f the "Plicy Restricted Applicatins" TLV: Tag Length Descriptin Presence '4F' 5-16 AID f the Plicy Restricted Mandatry Applicatin (e.g. PPSE) '4F' 5-16 AID f the Plicy Restricted Optinal Applicatin Table 3-1: Plicy Restricted Applicatins TLV Value Descriptin 3.4. Applicatin Discretinary Data This Applicatin Discretinary data is accessible t the CRS Applicatin and CREL Applicatins, if any, fr prprietary usage Applicatin Family The Applicatin Family indicates the sectr f industry that a Cntactless Applicatin belngs t. This indicatr may be used t grup tgether the Applicatins f the same family fr a similar prcess such as presenting nly ne family f Applicatins t the user. A Cntactless Applicatin shall belng t a primary family nly. The Applicatin Family is cded as the AFI defined in Table 12 f ISO/IEC [1]. The Applicatin Family applies t all Applicatins, regardless f prtcl type. The OPEN shall nt enfrce that the Applicatin Family and the AFI defined in sectin 4.7 are the same Display Required Indicatr The Display Required Indicatr TLV is an ptinal TLV assigned t an Applicatin s that it can indicate whether r nt it is able t perfrm a cntactless transactin even when the display is nt available. This parameter is nt evaluated by the OPEN. If this TLV is nt present, the Applicatin is indicating that it requires a display t perfrm the cntactless transactin.

18 18/77 Card Specificatin v2.2 - Amendment C - Cntactless Services The table belw defines the value part f the "Display Required Indicatr" TLV: Value '00' '01' Descriptin Applicatin requires a display Applicatin des nt require a display Table 3-2: Display Required Indicatr TLV Value Descriptin NOTE: This indicatr may be used by the CRS and/r CREL Applicatins fr their wn business purpses Applicatin Grups Definitin and Scpe An Applicatin Grup is cmpsed f ne and nly ne Head Applicatin and ne r mre Member Applicatins. The Head Applicatin is assciated with a Grup Authrizatin List defining the pssible membership f the grup as a list f AIDs. Applicatins referenced (by AID) in this list may request t jin the grup. An Applicatin shall nt be a member f mre than ne Applicatin Grup. An Applicatin that is neither a Head Applicatin, nr a member f an Applicatin Grup, is a Standalne Applicatin. At any time, a Standalne Applicatin may register itself as a Head Applicatin, hence defining a new Applicatin Grup, r as the member f an Applicatin Grup. The fllwing Cntactless Activatin States are used thrughut this specificatin; ACTIVATED, DEACTIVATED, NON_ACTIVATABLE. These states are defined in sectin 8.1. Grup Transprt: Sample -Lyalty Prgram Activated -Transprt Deactivated -Credit Issuer A Activated -Credit Issuer B Deactivated -Credit Issuer C Activated -Transprt -Air Service -Rail Service AID 1 Visible Deactivated AID 2 Invisible Deactivated AID 3 Invisible Deactivated Grup Credit Issuer A: -Dmestic -Internatinal AID 4 Visible Activated AID 5 Invisible Activated Figure 3-1: Applicatin Grup Head Applicatin The Head Applicatin: Establishes Cntactless Prtcl Parameters (see sectin 4.3) and priritizatin fr the member Applicatins. It is the respnsibility f the Applicatin Prvider f the Head Applicatin t persnalize the Head Applicatin with Cntactless Prtcl Parameter values that supprt all f the members applicatins named in its Grup Authrizatin List. When the Head Applicatin is set t the ACTIVATED state, all the Member Applicatins shall be set t the ACTIVATED state unless they are in the NON_ACTIVATABLE state.

19 Card Specificatin v2.2 - Amendment C - Cntactless Services 19/77 When the Head Applicatin is set t the DEACTIVATED state, all the Member Applicatins shall be set t the DEACTIVATED state, unless the Member Applicatin is in the NON_ACTIVATABLE state. When the Head Applicatin is set t the NON_ACTIVATABLE state, all the Member Applicatins shall be set t the DEACTIVATED state, unless the Member Applicatin is in the NON_ACTIVATABLE state. When the Head Applicatin is deleted, Applicatins previusly belnging t this Applicatin Grup becme Standalne Applicatins. All the frmer Member Applicatins shall be set t the DEACTIVATED state, unless the frmer Member Applicatin is in the NON_ACTIVATABLE state Member Applicatins Member Applicatins: Cntactless Prtcl Parameters (see sectin 4.3) and priritizatin are prvided by the Head Applicatin, even if the Member Applicatin was persnalized with its wn parameter values. When a member applicatin is set t the NON_ACTIVATABLE state, nly that applicatin becmes NON_ACTIVATABLE. The ther members f the grup fllw the activatin state f the Head Applicatin. When a Member Applicatin is in the NON_ACTIVATABLE state, it shall remain in the NON_ACTIVATABLE state even if the Head Applicatin is set t the ACTIVATED state. When the NON_ACTIVATABLE member is set t any state ther than NON_ACTIVATABLE, it fllws the activatin state f the Head Applicatin Jining r Leaving an Applicatin Grup The "Head Applicatin" TLV allws an Applicatin t request t be member f a grup by prviding the AID f the Head Applicatin f the Grup r t leave an Applicatin Grup using INSTALL [fr install], INSTALL [fr install and make selectable] r INSTALL [fr registry update]. An Applicatin may itself request t jin r leave an Applicatin Grup using the CRS API. The table belw defines the value part f the "Head Applicatin" TLV. Tag Length Value descriptin '4F' 5-16 AID f the grup s Head Applicatin t jin. Table 3-3: Head Applicatin TLV Descriptin The fllwing rules apply when jining an Applicatin Grup: The OPEN checks that the applicatin des nt yet belng t a grup. If the requested Head Applicatin is present, then the OPEN checks that the applicatin requesting t jin a grup has its AID listed in crrespnding Grup Authrizatin List. If the requested Head Applicatin is nt present (i.e. specified Applicatin Grup des nt exist), the installatin des nt fail. The assciatin will be perfrmed at the time the Head Applicatin is installed and if the applicatin AID is listed in its Grup Authrizatin List. The rules fr the alignment f the activatin state f the Member Applicatin with the activatin state f the Head Applicatin are applied as detailed in sectin are applied. The Current Prtcl Parameters shall be recalculated as detailed in sectin 4.4 if the new Member Applicatin is in the ACTIVATED state at the time it jins the grup. This TLV shall nt be in the same cmmand data field as the "Add t the Grup Authrizatin List" r "Remve frm the Grup Authrizatin List" TLVs. The fllwing rules apply when leaving an Applicatin Grup: The Head Applicatin TLV shall be prvided with empty length.

20 20/77 Card Specificatin v2.2 - Amendment C - Cntactless Services The OPEN shall check that the Applicatin belngs t an Applicatin Grup. If yes, the Applicatin is remved frm the Applicatin Grup, therwise an errr status is returned. The Applicatin becmes a Standalne Applicatin The Applicatin shall be set t the DEACTIVATED state, unless the frmer Member Applicatin is in the NON_ACTIVATABLE state. The pririty f the Applicatin shall be set t the lwest pririty Add t the Grup Authrizatin List When present in the INSTALL [fr install], the INSTALL [fr install and make selectable], r the INSTALL [fr registry update] cmmand, the "Add t the Grup Authrizatin List" parameter (see Table 3-4) establishes the target applicatin as a Head Applicatin, by creating its Grup Authrizatin List r adding AIDs t the existing ne. A Head Applicatin may itself request t update its Grup Authrizatin List using the CRS API. The table belw defines the value part f the "Add t the Grup Authrizatin List" TLV. Tag Length Descriptin '4F' 5-16 AID f an Applicatin t be added t the Grup Authrizatin List '4F' 5-16 AID f an Applicatin t be added t the Grup Authrizatin List Table 3-4: Add t the Grup Authrizatin List Value Descriptin The fllwing rules apply t the list cntent: The OPEN checks that the Applicatin is nt a Member Applicatin f an Applicatin Grup. The OPEN des nt check fr the uniqueness f an AID in multiple Grup Authrizatin Lists. The installatin des nt fail if an AID in the Grup Authrizatin List is already assciated t anther grup r nt present. Partial AID matching is nt supprted. This TLV shall nt be in the same cmmand data field as the "Head Applicatin" TLV. If this TLV cntains the AID f an Applicatin that already exists in the Grup Authrizatin List f the Head Applicatin, n errr is reprted and n ntificatins are made Remve frm the Grup Authrizatin List When present in the INSTALL [fr registry update] cmmand, the "Remve frm the Grup Authrizatin List" parameter (see Table 3-5) is used t remve ne r mre AIDs frm the Grup Authrizatin List. A Head Applicatin may itself request t update its Grup Authrizatin List using the CRS API. If an AID that was remved frm the Grup Authrizatin List refers t a Member Applicatin, that Applicatin: is remved frm the grup becmes a Standalne Applicatin shall be set t the DEACTIVATED state, unless the frmer Member Applicatin is in the NON_ACTIVATABLE state. and its pririty shall be set t the lwest pririty If the Grup Authrizatin List becmes empty, this Head Applicatin becmes a Standalne Applicatin.

21 Card Specificatin v2.2 - Amendment C - Cntactless Services 21/77 The table belw defines the value part f the "Remve frm the Grup Authrizatin List" TLV. Tag Length Descriptin '4F' 5-16 AID f an Applicatin t be remved frm the Grup Authrizatin List '4F' 5-16 AID f an Applicatin t be remved frm the Grup Authrizatin List Table 3-5: Remve frm Grup Authrizatin List Value Descriptin This TLV shall nt be in the same cmmand data field as the "Head Applicatin" TLV. If this TLV cntains the AID f an Applicatin that des nt exist in the Grup Authrizatin List f the Head Applicatin, n errr is reprted and n ntificatins are made CREL Applicatin Definitin and Scpe The Cntactless Registry Event Listener (CREL) Applicatin is an n-card Applicatin implementing specific business rules fr a specific set f Cntactless Applicatins. The CREL Applicatin is referenced by ne r several Applicatins during their installatin prcess. The CREL Applicatin shall be ntified by the OPEN after any change t the Registry entry f any referencing Applicatin. The CREL Applicatin shall implement and expse the CRELApplicatin interface. The actins, if any, taken by the CREL Applicatin upn receipt f the ntificatin are ut f the scpe f this dcument CREL Applicatin Registratin During the installatin prcess, during Registry update, r using the CRS API, any Applicatin may indicate t the OPEN a list f CREL Applicatins that shall be ntified f Registry events ccurring t the applicatin, by using the CREL List TLV structure (see Table 3-6). If a referenced CREL Applicatin is nt present r des nt implement nr expse the CRELApplicatin interface, the INSTALL cmmand des nt fail fr any f these reasns, hwever, this Applicatin will nt be ntified. If the CREL Applicatin is installed later, and it implements and expses the CRELApplicatin interface, it will receive ntificatins. The CREL Applicatin shall be able t retrieve the list f all the Applicatins that are referencing it. The CREL Applicatin shall be able t retrieve the Registry entry f each Applicatin that references it and read the cntent f the entry withut any specific Privilege. The CREL Applicatin may deactivate an Applicatin referencing it. The CREL Applicatin shall nt be able t make any ther change t the Registry entries f referencing Applicatins Add t the CREL List When present in the INSTALL [fr install], the INSTALL [fr install and make selectable], the INSTALL [fr registry update] cmmand, r using the CRS API, the "Add t the CREL List" parameter (see Table 3-6) prvides the list f AIDs f CREL Applicatins that shall be ntified by the OPEN upn any change in the GPRegistryEntry f the target Applicatin. The OPEN shall be able t retrieve the list f all CREL Applicatins that an Applicatin is referencing.

22 22/77 Card Specificatin v2.2 - Amendment C - Cntactless Services The table belw defines the value part f the "Add t the CREL List" TLV. Tag Length Descriptin '4F' 5-16 AID f a CREL Applicatin that shall be added t the CREL List '4F' 5-16 AID f a CREL Applicatin that shall be added t the CREL List Table 3-6: Add t the CREL List Value Descriptin The fllwing rule applies t the ntificatin list: The newly added CREL Applicatin is ntified. If the AID f a CREL Applicatin in the CREL List was previusly added, n errr is reprted and n ntificatins are made Remve frm the CREL List When present in the INSTALL [fr registry update] cmmand r using the CRS API, the "Remve frm the CREL List" parameter (see Table 3-7) prvides the list f AIDs f CREL Applicatins that shall be remved frm the ntificatin list f that Applicatin. The table belw defines the value part f the "Remve frm the CREL List" TLV. Tag Length Descriptin '4F' 5-16 AID f a CREL Applicatin that shall be remved frm the CREL List '4F' 5-16 AID f a CREL Applicatin that shall be remved frm the CREL List Table 3-7: Remve frm the CREL List Value Descriptin The fllwing rule applies t the ntificatin list: The remved CREL Applicatin is ntified. If the AID f a CREL Applicatin des nt exist in the CREL List, n errr is reprted and n ntificatins are made CRS Applicatin Definitin and Scpe The Cntactless Registry Service (CRS) Applicatin is respnsible fr prviding the user with means t retrieve a list f all Applicatin Grups and Standalne Applicatins, and t activate, deactivate, r change the Pririty r Vlatile Pririty f these entities n the cntactless interface. When present, the CRS Applicatin shall be accessible by the n-card Applicatins t request switching their wn Availability state t ACTIVATED (see sectin 8.1). The fllwing requirements apply: Only ne CRS Applicatin shall exist per secure element. The Cntactless Activatin Privilege and the Glbal Registry Privilege must be assigned t the CRS Applicatin. These privileges allw the CRS Applicatin t successfully invke the CRS API t

23 Card Specificatin v2.2 - Amendment C - Cntactless Services 23/77 retrieve a list f all Applicatins, activate r deactivate these Applicatins, change the Pririty r Vlatile Pririty f these Applicatins n the cntactless interface (see sectin 6) glbally switch n r ff the cntactless interface (see sectin 8.3) The CRS Applicatin shall implement and expse the CRSApplicatin Interface. The CRSApplicatin.prcessCLEvent() methd shall be called by the OPEN fr each activatin requested by an Applicatin withut the Cntactless Self-Activatin Privilege. The reference t the CL registry entry f the targeted Applicatin, which was passed as a parameter f CRSApplicatin.prcessCLEvent(), can be used by the CRS Applicatin t retrieve the list f cnflicting Applicatins. The behavir f the CRSApplicatin.prcessCLEvent()methd is ut f scpe f this specificatin. A CRS Applicatin which is installed with the reserved AID fr the GlbalPlatfrm CRS Applicatin shall supprt the APDU cmmand set described in sectin Ntificatin Rules General Rules When a pwer lss ccurs, and all Applicatins have nt all been ntified f the last Registry mdificatin, the fllwing rules apply: If n transactin was pen at the time f the pwer lss, ntificatins shall be issued fr all Applicatins. If a transactin was pen at the time f the pwer lss, previus mdificatins t the Registry are rlled back and the issuance f the ntificatins is nt restarted. Hwever, it is strngly recmmended nt t pen such a transactin due t the peratins ptentially perfrmed by ntified Applicatins. The rder f ntificatin is nt defined. Applicatins shuld be aware that they may be ntified again in the case f pwer lss CREL Ntificatin CREL Applicatins referenced by an Applicatin, 'A', are ntified when the Applicatin 'A': switches t the Lifecyle State INSTALLED, SELECTABLE, r LOCKED is unlcked r deleted switches t the Availability State ACTIVATED, NON_ACTIVATABLE, DEACTIVATED has any f its Cntactless Prtcl Parameters (see Table 11-3) updated has any f its User Interactin parameters (see Table 11-5) updated A CREL Applicatin shall nt be ntified when it is the riginatr f an event. See Annex A, CRS API, where the details f the crrespnding GlbalPlatfrm Events that are used fr ntificatins are described.

24 24/77 Card Specificatin v2.2 - Amendment C - Cntactless Services CRS Ntificatin The CRS Applicatin shall be ntified abut all Registry changes (as defined fr CREL Applicatins, see sectin ) ccurring t any Applicatin when it is nt the riginatr fr the event. Unlike a CREL Applicatin, the CRS Applicatin des nt need t be registered fr any Applicatin in rder t be ntified abut a Registry change fr any Applicatin Applicatin Ntificatins Applicatins that implement the CLApplet interface shall be ntified f changes ccurring t their Registry entry. An Applicatin shall nt be ntified when it is the riginatr f an event GlbalPlatfrm CRS Applicatin Definitin and Scpe The GlbalPlatfrm CRS Applicatin, if present, shall implement the APDU set as defined in this sectin: an APDU t get infrmatin n registered Cntactless Applicatins and their respective Cntactless Registry parameters an APDU t: activate/deactivate Cntactless Applicatins and t respnd with the list f cnflicting Applicatins' AIDs establish the rder f Applicatins in the GlbalPlatfrm Registry. It shall be able t receive a list f Applicatin AIDs (Head Applicatins, Member Applicatins, r Standalne Applicatins) setup/discard the Vlatile Pririty (see sectin 6.2) The fllwing AIDs are reserved by GlbalPlatfrm fr the purpse f installing the GlbalPlatfrm CRS Applicatin: Executable Lad File AID: 'A ' Executable Mdule AID: 'A ' Applicatin AID: 'A ' The standard GlbalPlatfrm CRS Applicatin is defined in this specificatin as a pssible implementatin fr a CRS Applicatin. It shall be able t prcess the APDU cmmands described in sectins and , therefre prviding the "user" with expected management capabilities as described in sectin 3.9. The GlbalPlatfrm CRS Applicatin cannt be a Security Dmain because f the redefinitin f the GET STATUS and SET STATUS cmmands in sectin 11. Parameters are accessed thrugh the GET STATUS and SET STATUS cmmands TLV fr User Interactin Parameters The TLVs described belw identify each User Interactin parameter accessed by the GlbalPlatfrm CRS Applicatin. These TLVs may be used with the GET STATUS cmmand (see sectin ) as search r filter criterin. The descriptin f each tag in Table 3-8, belw, indicates which tag may be used with which cmmand. Filter Criteria (FC) are prvided within tag list '5C' and are used t build the respnse field f the GET STATUS cmmand. Search Criteria (SC) apply t the incming data field f the GET STATUS cmmand.

25 Card Specificatin v2.2 - Amendment C - Cntactless Services 25/77 User Interactin Parameter Tag Length GET STATUS Sectin SC FC Applicatin AID '4F' 5-16 Yes Yes Applicatin Lifecycle state '9F70' 2 Yes Yes Display Cntrl Template '7F20' var N Yes 3.2 Unifrm Resurce Lcatr '5F50' var N Yes 3.2 Applicatin Image '5F44' var N Yes 3.2 Display Message '5F45' var N Yes 3.2 Applicatin Update Cunter '80' var N Yes Pririty Indicatr '81' var Yes Yes Grup Head Applicatin 'A2' var Yes Yes Grup Member s Applicatin 'A3' var N Yes CREL Applicatin AID List 'A4' var N Yes Plicy Restricted Applicatins 'A5' var Yes Yes 3.3 Applicatin Discretinary Data 'A6' var N N 3.4 Applicatin Family '87' var Yes Yes 3.5 Display Required Indicatr '88' 1 Yes Yes 3.6 Cntinuus Prcessing '8A' var N Yes 6.4 Recgnitin Algrithm '8B' var N Yes 6.5 Assigned Prtcls '8C' var N Yes 6.6 Table 3-8: User Interactin parameters Tag Usage These tags shall be used as search r filter criteria in a simple, nn-cnstructed frm. Fr example, '5F50' is a sub-tag f '7F20', hwever, in the search r filter criteria data field nly '5F50' shall appear (see the example related t Table 3-14) Applicatin AID The Applicatin AID tag '4F' is a mandatry tag within the Cntactless Registry and can be used bth as a search criterin and in the tag list. Partial AID matching is supprted when this tag is used as a search criterin in the GET STATUS cmmand (see sectin ) Applicatin Lifecycle State The Applicatin Lifecycle State tag '9F70' prvides the Applicatin Lifecycle state n the first byte as defined in GP2.2 [0]. The Cntactless Activatin State is encded n the secnd byte as defined in Table 8-1. The Applicatin Lifecycle State tag can be used bth as a search criterin and in a tag list. When tag '9F70' is used as a search criterin: Applicatin-specific lifecycle state bits in the first byte shall be ignred RFU bits in the secnd byte shall be ignred Update Cunters The CRS maintains a cunter in the range frm 0 t fr each registered Applicatin. The cunters initially shall be set t zer. Fr each update made t the Registry entry f an Applicatin, the crrespnding cunter shall be incremented by ne and managed cyclically.

26 26/77 Card Specificatin v2.2 - Amendment C - Cntactless Services Additinally, the CRS maintains a glbal cunter in the range frm 0 t This cunter, which is als initially set t zer, is incremented each time an Applicatin cunter is created, deleted r incremented. This cunter is als managed cyclically. These cunters can be used by n-card r ff-card entities t detect that changes have ccurred in the Registry and t synchrnize their wn state. The GlbalPlatfrm CRS Applicatin allws retrieval f these parameters thrugh an APDU Cmmand respnse. The Glbal Update Cunter is returned in the respnse f the SELECT cmmand. The encding f the tag s class is SELECT-cmmand specific (see sectin ). The Applicatin Update Cunter is retrieved using the GET STATUS cmmand respnse data. A TLV can be used in the tag list as filter criterin Selectin Pririty The Selectin Pririty indicates the rder in which Cntactless Applicatins will be cnsidered during partial selectin ver the cntactless interface (see sectin 6.2). The Selectin Pririty is calculated based n the abslute psitin f the Cntactless Applicatin's entry in the GlbalPlatfrm Registry, and the Vlatile Pririty, if assigned. Cntactless Applicatins that are assigned Vlatile Pririty are given the highest pririty. When cmputing the abslute psitin, bth Cntactless and Nn-Cntactless Applicatins are taken in t accunt. The Selectin Pririty is cded n ne byte. The value f 0 crrespnds t the highest pririty Applicatin Grup In Figure 3 1: Applicatin Grup, tw TLVs are used t indicate the gruping relatinship as fllws: TLV Applicatin Grup Head (AID f the Head Applicatin); this tag can be used as a search criterin t retrieve the Applicatin Grup Membership List. TLV Applicatin Grup Membership List; this tag can be used in the tag list. This is a list f AIDs f Applicatins that have successfully jined the grup CREL Applicatin AID List The TLV CREL Applicatin AID List prvides infrmatin related t the CREL Applicatin(s) referenced by an Applicatin. The CREL Applicatin AID List is a cnstructed TLV with at least ne mandatry tag '4F' which prvides the AID f a CREL Applicatin. The TLV has the fllwing structure: TLV CREL Applicatin AID List (Template cnstructed tag with sub-data elements) cntains the AID(s) f the CREL Applicatin(s) as sub-data elements. Tag '4F': AID f 1 st CREL Applicatin Tag '4F': AID f 2 nd CREL Applicatin When used as a search criterin, the CREL Applicatin AID List shall cntain nly ne AID.