NXP Semiconductors
MF3D(H)x2
MIFARE DESFire EV2 contactless multi-application IC
MF3Dx2_MF3DHx2_SDS All information provided in this document is subject to legal disclaimers. © NXP B.V. 2018. All rights reserved.
Product short data sheet Rev. 3.1 — 17 May 2018
COMPANY PUBLIC 364231 12 / 27
MIFARE DESFire EV2 offers a transaction oriented backup mechanism to prevent
inconsistent updating of data storage across multiple files during a tearing situation.
When transaction tearing occurs, either all data fields are updated or none is altered.
Besides the application file structure support, MIFARE DESFire EV2 offers many optional
features such as following:
• Delegated Application Management (MIsmartApp) for giving rights to third party
application creation and management.
• Multiple key set within an application with key rolling mechanism and key migration
supported.
• Shared files between two applications, supporting a single transaction over two
applications at the same time.
• Multiple keys for each access rights of files.
• Transaction MAC on application level, MACing the transacted data with a secret key on
the card and served as a proof of transaction to the backend system.
• Virtual Card Architecture providing a privacy protecting mechanism during card
selection.
• Proximity Check to prevent against relay attacks.
• Originality Check for verification of genuine MIFARE DESFire EV2 product from NXP or
its licensees.
The following chapters will provide basic description of some functionality on MIFARE
DESFire EV2. For a morel details description of each functionality on MIFARE DESFire
EV2, please see [1].
8.2 Contactless energy and data transfer
In the MIFARE product-based system, the MIFARE DESFire EV2 is connected to a coil
consisting of a few turns embedded in a standard ISO/IEC smart card. A battery is not
needed. When the card is positioned in the proximity of the PCD antenna, the high speed
RF communication interface allows data to be transmitted up to 848 kbit/s.
8.3 Anti-collision
An intelligent anti-collision mechanism allows more than one MIFARE DESFire EV2 in
the field to be handled simultaneously. The anti-collision algorithm selects each MIFARE
DESFire EV2 individually and ensures that the execution of a transaction with a selected
MIFARE DESFire EV2 is performed correctly without data corruption resulting from other
MIFARE DESFire EV2s in the field.
8.4 UID/serial number
The unique 7 byte (UID) is programmed into a locked part of the NV memory which is
reserved for the manufacturer. Due to security and system requirements these bytes
are write-protected after being programmed by the IC manufacturer at production time.
According to ISO/IEC 14443-3 during the first anti-collision loop the cascade tag returns
a value of 88h and also the first 3 bytes of the UID, UID0 to UID2 and BCC. The second
anti-collision loop returns bytes UID3 to UID6 and BCC.
UID0 holds the manufacturer ID for NXP (04h) according to ISO/IEC 14443-3 and ISO/
IEC 7816-6 AMD 1.
