Mobile Contactless Multi-Protocol - Centre d'information AFSCM

Mobile Contactless Multi-Protocols Implementation Guidelines

RELEASE 1.3.1 Date

28/03/2013

Reference

130328 - AFSCM TECH - LIVBL - Multi protocol for interoperability - v1.3.1.doc

Mobile Contactless Multi-Protocol - v1.3.1 – AFSCM Confidential & Proprietary

p1/16

Role

Name

Company

Authors

Sophie Diallo Thierry Simon Frédéric Loinard Ahmad Saif Gaël Gérard Saïd Benlaadam Fahd el Caidi David Cortés Grégoire Fraisse Gaël Gérard Laurence Becq

Bouygues Telecom EI Telecom

Editor Document manager Approval

Orange SFR AFSCM AFSCM AFSCM

Document management Name

Chapters

Modification

0.1 0.2

Version

05/12/2010 03/01/2011

Date

F. Loinard F. Loinard

All document All document

1.0.1

07/02/2011

All document

1.0.2

15/02/2011

1.0.3

07/03/2011

1.0.4

27/05/2011

1.1

03/10/2011

1.2.1 1.2.2 1.3.1

12/10/2011 13/12/2011 28/03/2013

F. Loinard, A. SAIF F. Loinard, A. SAIF F. Loinard A. SAIF F. Loinard A. SAIF F. Loinard A. SAIF L. Rozak A. SAIF A. SAIF G.Gérard

Document creation Alignment with PayPass recommendations in CLF PN544 specification Comments integration of manufacturers (ACS, Gemalto, FIME)

All document All document All Document All Document

Comments integration Comments integration Comments Integration Integration of output of the Gemalto-Orange Labs WS (§3.1.5)

All Document All Document 1.3

Editorial update of the document Editorial update of the document New references to EMVCo and ISO 14443-2 documents

2.1

Suppression du support de MiFare 4k

3.1.2 & 3.2.2.1 Type A and B parameters and mask values changed


p2/16

Table of contents DOCUMENT MANAGEMENT.............................................................................................................................. 2 1. INTRODUCTION ............................................................................................................................... 5 1.1. 1.2. 1.3. 1.4.

PURPOSE OF THE DOCUMENT................................................................................................................. 5 SCOPE OF THE DOCUMENT ..................................................................................................................... 5 REFERENCES ............................................................................................................................................ 5 ACRONYMS AND ABBREVIATIONS........................................................................................................... 6

2. TECHNICAL BACKGROUNDS ............................................................................................................. 8 2.1. SUPPORTED TECHNOLOGIES ................................................................................................................... 8 2.2. INITIALIZATION AND ANTI COLLISION ..................................................................................................... 8 2.3. SUPPORTED CONFIGURATIONS ............................................................................................................... 8 2.4. PCD-PICC INTERFACE ............................................................................................................................... 8 2.4.1. POLLING ................................................................................................................................................ 8 2.4.2. SEQUENCE CHART OF 14443-4 TYPE A ................................................................................................. 9 2.4.3. CARD IDENTIFICATION ISO14443-3 TYPE A ....................................................................................... 10 2.4.4. SEQUENCE CHART OF 14443-4 TYPE B ............................................................................................... 11 3. CONTACTLESS PARAMETERS .......................................................................................................... 12 3.1. TYPE A .................................................................................................................................................... 12 3.1.1. Definitions .......................................................................................................................................... 12 3.1.2. Mandatory parameters for TYPE A ..................................................................................................... 12 3.2. TYPE B .................................................................................................................................................... 13 3.2.1. Definitions .......................................................................................................................................... 13 3.2.2. Mandatory parameters for TYPE B ..................................................................................................... 14 4. NFC PEER TO PEER MODE .............................................................................................................. 15 5. CONTACTLESS PROXIMITY PCD ...................................................................................................... 16 5.1. REQUIREMENTS ..................................................................................................................................... 16 5.2. EMV CONTACTLESS SPECIFICATIONS FOR PAYMENT SYSTEMS ............................................................ 16 5.2.1. Contactless Communication Protocol – Contactless Level 1.............................................................. 16 5.2.2. Contactless Mobile Payment (PICC) ................................................................................................... 16 5.2.3. Terminal (PCD).................................................................................................................................... 16


p3/16

Table of illustrations 1. 2. 3. 4. 5. 6. 7. 8. 9. 10.

References .................................................................................................................................................. 6 Acronyms and abbreviations...................................................................................................................... 7 14443-4 TYPE A sequence chart ................................................................................................................. 9 14443-3 TYPE A card identification .......................................................................................................... 10 14443-4 TYPE B sequence chart ............................................................................................................... 11 Registry entries for TYPE A ....................................................................................................................... 12 Contactless parameters............................................................................................................................ 12 Mandated contactless parameters .......................................................................................................... 13 Registry entries for a TYPE B RF technology card .................................................................................... 13 NFC parameters and associated mask ..................................................................................................... 14


p4/16

1. 1.1.

Introduction Purpose of the document

This document makes recommendations to handset/uicc manufacturers and to Proximity Coupling Device (PCD) manufacturers to ensure their interoperability. The NFC paradigm is built upon the multi-application concept. The NFC mobile handset and UICC combination needs to be compliant with several infrastructures (e.g. payment, access control, public transportation …) whereas a contactless card is compliant with a single infrastructure. ISO/IEC 14443 [2], [3], [4] specifications are composed of a set of parameters and options. The main objective of this document is to have a configuration in line with these standard specifications and that allows the UICC hosting all type of data and applications (e.g.: Mifare Classic, Mifare DESfire, payment applications compatible with EMVCo, all standard TYPE A and B applications) This document does NOT define any new parameter that is not compliant with standard specifications. Note: a standard type A application is an application that is addressable by a PCD using ISO/IEC 14443-4 type A protocol. The same way, a type B application is addressable using ISO/IEC 14443-4 type B protocol.

1.2.

Scope of the document

This document is limited to the card emulation mode and peer-to-peer mode. It also sets out requirements for the Proximity Coupling Device (PCD) that interacts with the NFC Handset and UICC. This document is built upon the objective that usage of NFC compatible devices shall be as simple as possible for the end user. All contactless services that this latter has subscribed to shall be compatible. No activation/deactivation operations due to contactless parameters conflict is requested to the user. This hypothesis leads to make technical decision to exclude the compatibility of deployed technologies. Note: UICC contactless parameters shall not be modified when installing/activating contactless services by using [8] capabilities.

1.3.

References

Ref

Title

Document Reference

Version

[1] [2] [3] [4] [5] [6] [7] [8]

NFCForum-TS-DigitalProtocol-1.0 ISO/IEC 14443-2 ISO/IEC 14443-3 ISO/IEC 14443-4 ETSI TS 102 622 MIFARE ISO/IEC 14443 PICC Selection MIFARE Type Identification Procedure GlobalPlatform Card Specification V2.2 Amendment C EMV Contactless Specifications for Payment Systems

Digital 1.0 (17 November 2010) ISO/IEC 14443-2 (2010) ISO/IEC 14443-3 (2011) ISO/IEC 14443-4 (2008) ETSI TS 102 622 Release 9 NXP AN 10834 (26 June 2009) NXP AN10833 (29 August 2011) GPC_SPE_025 (February 2012)

1.0 Ed 2

[9]

Ed 2 V9.4.0 Revision 3.0 Revision 3.2 v1.0.1

Book D: Contactless Communication V2.2 Protocol (June 2012)


p5/16

[10] ISO/IEC 14443-2 [11] EMVCo handset requirements

[12] EMVCo Test Equipment Specifications

ISO/IEC: Amendment 2 2011 EMVCo Handset Requirements for Version1.0 Contactless Mobile Payment (June 2010) Level 1 Test Equipment Specifications - v2.0 PICC Manual, PCD Manual, CMR Manual, Gerber Files 1. References

1.4.

Acronyms and Abbreviations Abbreviation

1K AFI AFSCM ADC ATQA ATQB ATS ATTRIB CID CLF CRC_B DR DS EMVCo EOF FO FSCI FSD FSDI FWI GP LSB MBLI MNO MSB NA NAD NFC OS P2P PCD PICC PPS RATS REQA REQB

Wording

1K bytes for Mifare Application Family Identifier. Association Française du Sans Contact Mobile Application Data Coding Answer To reQuest, TYPE A Answer To reQuest, TYPE B Answer To Select PICC Selection Command Card Identifier Contactless Front End Cycling Redundancy Check (to remove) Divisor Receive (PCD to PICC) Divisor Send (PICC to PCD) Europay Mastercard Visa Contactless End of Frame Frame Option Frame Size for proximity Card Integer Frame Size for proximity coupling Device Frame Size for proximity coupling Device Integer Frame Waiting time Integer Global Platform Least Significant Bit Maximum Buffer Length Index Mobile Network Operator Most Significant Bit No Applicable Node Address Near Field Communication Operating System Peer To Peer Proximity Coupling Device Proximity Integrated Circuit Card Protocol and Parameter selection Request for Answer to Select REQuest command, TYPE A REQuest command TYPE B


p6/16

RFU SAK SFGI SFGT SOF S(WTX) T=CL T0 TA(1) TB(1) TC(1) TR2 UICC UID UID0

Reserved for future Use ISO/IEC Select AcKnowledge Start-up Frame Guard time Integer Start-up Frame Guard Time Start Of Frame S-block request for Waiting Time Extension Transport layer protocol = Contact Less; defined in ISO/IEC 14443-4 Header Byte ATS : First byte Interface Character ATS : Second byte Interface Character ATS : Third byte Interface Character Timing before PCD Start-of-Frame Universal Integrated Circuit Card (usually known as SIM card) Unique Identifier Unique Identifier byte 0 2. Acronyms and abbreviations


p7/16

2. 2.1.

Technical backgrounds Supported technologies

The handset shall be compliant with all the following RF protocols without any action from the end user (no switch between two configurations/applications by the user): ISO14443-3: Mifare Classic 1K ISO14443-4: TYPE A (including Mifare DESFire EV1), ISO 14443-4 TYPE B Note: For TYPE A, only double size UID (7 bytes) is supported

2.2. Initialization and anti collision Both TYPE A (including Mifare Classic and Mifare DESfire) and TYPE B products shall support initialization and anti-collision as defined by ISO/IEC 14443-3.

2.3. Supported configurations For TYPE A, the default contactless profile of the UICC (or any other Secure Element) shall be the profile that complies with EMVCo requirements (cf section 3.1.2.2) Moreover, some UICC from specific MNO shall support Mifare Classic and Mifare DESfire applications. These UICC shall support all of the following configurations:  EMVCo + Mifare DESFire EV1  EMVCo + Mifare classic 1K  EMVCo + Mifare Classic 1K + Mifare DESFire EV1 For more details, please refer to section 3.1.2.2 For TYPE B, there shall be one and only one configuration independently of the activated applications on the UICC . This configuration is compliant with EMVCo recommendations and all fully standard applications (e.g.: Calypso release 3.1, …).

2.4. PCD-PICC Interface 2.4.1. Polling In order to detect PICCs which are in the RF Field, a PCD shall send repeated Request Commands. The PCD shall send REQA and REQB. The REQA or REQB has to be sent after the carrier is switched on, waiting time 5 milliseconds before starting the transmission. The minimum required time between a REQA and a REQB or REQB and REQA is 5 milliseconds. The PCD must stop the communication protocol, if no associated application is answering… Please refer to standards ISO/IEC 14443-3 and ISO/IEC 14443-4 for more information


p8/16

2.4.2. Sequence chart of 14443-4 TYPE A PCD

PICC

REQA

ATQA

The mobile Phone indicates the UID length and some proprietary bits

The PCD performs one or two cascade levels Anticollision loop

SAK

The mobile Phone indicates its support of 14443-4 & Mifare Card family

Setting of the maximum frame Size (FSDI) and CID RATS

ATS

The mobile Phone indicates its bit rate capability, FWT, Max Frame size & Extended Parameters support

Optional Setting of higher bit rates PPS Acknowledgement Response

3. 14443-4 TYPE A sequence chart


p9/16

2.4.3. Card Identification ISO14443-3 TYPE A MifareClassic ISO14443-4( TYPE A or Mifare DESFire EV1 ) ,Card Activation

No

ATQA Bit 8 = 1 ?

ATQA Bit 7 = 1 ?

No

Yes Anticollision Loop (two cascade levels) CL2

Anticollision Loop (one cascade level )

Yes Yes

No

SAK Bit 2 = 1 ?

Yes

SAK Bit 5 = 1 ?

SAK Bit 6 = 1 ?

SAK = 20

RFU or Other Card

Type A or Mifare DESFire EV1

SAK Bit 6 = 1 ?

Yes

Yes

No

Yes

No

No

SAK Bit 4 = 1 ?

No

Yes

SAK Bit 5 = 1 ?

No

SAK = 28

SAK = 08

Mifare Classic

Type A & Mifare Classic

RFU or Other Card

4. 14443-3 TYPE A card identification Mobile Contactless Multi-Protocol - v1.3.1 – AFSCM Confidential & Proprietary

p10/16

2.4.4. Sequence chart of 14443-4 TYPE B PCD

PICC

REQB

ATQB The PCD sets the bit rate, the max frame, TR0/ TR1,suppression or not of SOF/EOF & the support of 14443-4

ATTRIB

ATA

The mobile Phone indicates ist bit rate capabilities, FWT, Max Frame size & extended parameters support & the support of 14443-4

The mobile Phone indicates its MBLI (MaximumBuffer Length Index) & if support CID or not.

5. 14443-4 TYPE B sequence chart


p11/16

3.

Contactless Parameters

This part of the document describes the standard parameters for supported protocols.

3.1.

TYPE A 3.1.1.

Definitions

In the context of this section of the document, all parameters for ISO/IEC 14443-4 TYPE A are defined in the table below. Parameter MODE UID SAK ATQA APPLICATION_DATA FWI, SFGI CID_SUPPORT CLT_SUPPORT DATARATE_MAX

Comment TYPE A card emulation enabled indicator UID as defined in ISO/IEC 14443-3 [3] for TYPE A Preformatted SAK as defined in ISO/IEC 14443-3 [3] for TYPE A ATQA coded as defined in ETSI 102-622 [5] for TYPE A The historical bytes as defined in ISO/IEC 14443-4 [4] for TYPE A Frame Waiting time and Start-up frame guard Time as defined in ISO/IEC 14443-3 [4] for type A support for CID as defined ISO/IEC 14443-4 [4] Support of tunneling mode for ISO/IEC 14443-4 [7] non compliant protocols Maximum data rate supported 6. Registry entries for TYPE A

3.1.2.

Mandatory parameters for TYPE A

3.1.2.1. NFC parameters and associated mask The table below indicates the parameters used by each contactless technology. This table lists all recommended values for all listed protocols (the column headings in the first row of the table) N.B.: Please note that for ATQA, byte 1 contains bits from 1 to 8 and byte 2 contains bits from 9 to 16 as defined by [5] and [8] Basic profile (compatible with EMVco applications) GP Tag 80 81 82 83 84 85 86

Label LV UID UID SAK ATQA LV ATS ATS FWI/SFGI CID Data_Rate _Max

Length 1 0,4,7,10 1 2 1 0 to 15 1 1 3

NFC param Value (hex) 00 (random) 20 0400 00

00

78 01 000000

Mask Value (hex)

Mifare classic parameters (7 bytes UID) NFC param Value (hex)

Mask Value (hex) FF

F7 BFFC FF

07 (fixed value) 08 4400 00

FF FF FFFFFF

78 01 000000

DESFire EV1 (7 bytes UID) NFC param Value (hex)

Mask Value (hex) FF

FF FFFC FF

07 (fixed value) 20 4403 00

FF FF 000000

78 01 030300

FF FF 000000

F7 FFFF FF

7. Contactless parameters


p12/16

3.1.2.2.

Mobile Station implementation

The contactless parameters required for TYPE A of a NFC handset and UICC (Mobile Station – MS) are dependent on the contactless applications to be supported. If the MS does not support any Mifare applications and supports only standard type A applications, it shall be compliant with the profile number 1, also called the “Default profile”, as described in the table below. If, additionally, the MS supports Mifare Classic data, the MS shall be compliant with the profile number 2 as described in the table below. If in addition to the profile 1, the MS supports Mifare Desfire EV1 applications, the MS shall be compliant with the profile number 3 as described in the table below. If the MS supports standard type A, Mifare Classic data and Mifare Desfire EV1 applications, the MS shall be compliant with the profile number 4 as described in the table below.

GP Tag

Label

Length

80

LV UID UID

1 0,4,7,10

81 82 83

SAK ATQA LV ATS ATS FWI/SFGI CID Data_Rate _Max

1 2 1 0 to 15 1 1 3

84 85 86

20 0400 00

F7 BFFC 00

Profiles 2 - Default profile + Mifare 3 - Default profile + classic activated application Mifare DESFire activated application NFC param Mask Value NFC Mask Value Value (hex) (hex) param (hex) Value (hex) 07 FF 07 FF (fixed value) (fixed value) 28 FF 20 F7 4400 FFFC 4403 FFFF 00 00 00 00

78 01 000000

FF FF FFFFFF

78 01 000000

1 - Basic profile (compatible with EMVco applications) NFC Mask param Value Value (hex) (hex) 00 00 (random)

FF FF FFFFFF

78 01 000000

FF FF FFFFFF

4 - Default profile + Mifare +DESFire activated applications NFC param Mask Value Value (hex) (hex)

07 (fixed value) 28 4403 00

FF

78 01 000000

FF FF FFFFFF

FF FFFF 00

8. Mandated contactless parameters

3.2.

TYPE B 3.2.1.

Definitions

In the context of this section of the document, all parameters for ISO/IEC 14443-4 type A are defined in the table below. Identifier

Parameter

'01'

MODE

'02'

PUPI

'03'

AFI

'04'

ATQB

'05'

HIGHER_LAYER_RESPONSE

'06'

DATARATE_MAX

Comment TYPE B card emulation enabled indicator PUPI as defined in ISO/IEC 14443-3 [3] for TYPE B. Application family identifier as defined in ISO/IEC 14443-3 [3] for TYPE B Additional data for ATQB Higher Layer response in answer to ATTRIB command as defined in ISO/IEC 14443-3 [3] for TYPE B Maximum data rate supported

9. Registry entries for a TYPE B RF technology card


p13/16

3.2.2.

Mandatory parameters for TYPE B

3.2.2.1.

NFC parameters and associated mask

GP Tag 80 81 82 83 84

Label

Length

LV PUPI PUPI AFI ATQB GP LV ATTRIB Hlresp ATTRIB DATA_Rate_max

1 4 1 4 1 0 to 15 3

Fixed profile NFC param Mask Value Value (hex) (hex) 00 (Random) 00 00 FF 00000071 FFFFFFFF 00 000000

FF FFFFFF

10. NFC parameters and associated mask


p14/16

4.

NFC Peer to Peer Mode If P2P is supported, the device shall work in P2P with a bit rate higher than 212 Kbits/s (bigger values are allowed) in order to avoid interoperability problems with contactless readers up to 106 Kbits/s in TYPE A.


p15/16

5. 5.1.

Contactless Proximity PCD Requirements

The PCD must be compliant with the ISO/IEC 14443-2 and ISO/IEC 14443-3 standard. The Class 1, 2, 3 shall be supported as described in the ISO/IEC 14443-2: AMD4 Additional PICC class. In addition it shall support the “EMVCo type approval Contactless Level 1.

5.2.

EMV Contactless Specifications for Payment Systems 5.2.1.

Contactless Communication Protocol – Contactless Level 1

Reference specification: PayPass ISO/IEC 14443 Implementation Specification version 1.1 • Version 2.0.1

5.2.2.

Contactless Mobile Payment (PICC)

Reference specification: EMVCo Handset Requirements for Contactless Mobile Payment: Version1.0 June 2010

5.2.3.

Terminal (PCD)

Compliant with EMVCo Contactless Level 1.


p16/16