MF3ICD8101 NXP Semiconductors, MF3ICD8101 Datasheet - Page 5
![no-image](/images/manufacturer_photos/0/4/487/nxp_semiconductors_sml.jpg)
MF3ICD8101
Manufacturer Part Number
MF3ICD8101
Description
Mf3icd8101 Mifare Desfire Contactless Multi-application Ic
Manufacturer
NXP Semiconductors
Datasheet
1.MF3ICD8101.pdf
(12 pages)
NXP Semiconductors
MF3ICD8101_SDS_N_1
Objective short data sheet
8.5 Available file types
8.6 Security
8.7 3 pass authentication
The files within an application can be of different types as:
The 7 byte UID is unchangeably programmed into each device during production. It
cannot be altered and ensures the uniqueness of each device.
The UID may be used to derive diversified keys for each ticket. Diversified PICC keys
contribute to gain an effective anti-cloning mechanism.
Remark: For new authentications other than 0Ah, the init vector for the calculation of the
MAC is only reset to ‘00h’ after the authentication. So the init vector shall be remembered
during the whole transaction until a new authentication is calculated.
Prior to data transmission a mutual three pass authentication can be done between PICC
and PCD depending on the configuration employing either 56-bit DES (single DES, DES),
112-bit DES (triple DES, 3DES), 168-bit DES (3 key triple DES, 3K3DES) or AES. During
the authentication the security level of all further commands during the session is set.
Three pass authentication proves that both parties (PCD and PICC) are owner of a
common secret (DES, 3DES, 3K3DES. AES key). The result of a successful
authentication is a trusted link between both parties. The authentication command also
yields a session key that you can use to protect the data transmission channel.
•
•
•
•
•
Standard Data Files
Backup Data Files
Value Files with Backup
Linear Record Files with Backup
Cyclic Record Files with Backup
Rev. 01.00 — 11 December 2007
MIFARE DESFire contactless multi-application IC
MF3ICD8101
© NXP B.V. 2007. All rights reserved.
5 of 12