MF3ICD21, MF3ICD41, MF3ICD81
MIFARE DESFire EV1 contactless multi-application IC
If this rollback is necessary, it is done without user interaction before carrying out further commands. To ensure data integrity on application level, a transaction-oriented backup is implemented for all file types with backup. It is possible to mix file types with and without backup within one application. As the commands are the same for MF3ICD81, MF3ICD41 and MF3ICD21, the command details are available in Ref. 1. Only the memory size is different between the three devices.

Available file types
The files within an application can be any of the following types:
Standard data files Backup data files Value files with backup Linear record files with backup Cyclic record files with backup

Security
The 7 byte UID is fixed, 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 MIFARE DESFire EV1 keys contribute to gain an effective anti-cloning mechanism and increase the security of the original key see Ref. 6. Prior to data transmission a mutual three pass authentication can be done between MIFARE DESFire EV1 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 level of security of all further commands during the session is set. In addition the communication settings of the fileapplication result in the following options of secure communication between MIFARE DESFire EV1 and PCD: MF3ICD40)  backwards-compatible mode to MF3ICD40: 4 byte MAC, all other authentications based on DES3DESAES: 8 byte CMAC backwards-compatible mode to MF3ICD40: A 16-bit CRC is calculated over the stream and attached. The resulting stream is encrypted using the chosen cryptographic method. All other authentications based DES3DESAES: A 32-bit CRC is calculated over the stream and attached. The resulting stream is encrypted using the chosen cryptographic method. Find more information on the security concept of the product in Ref. 1. Be aware not all levels of security are recommended. The recommended secure handling of the product can be seen in Ref. 2 and in Ref. 10.

MF3ICD21, MF3ICD41, MF3ICD81
MIFARE DESFire EV1 contactless multi-application IC
DESFire command set
Table 4. Command REQA WUPA ANTICOLLISIONSELECT Cascade Level 1 ISOIEC 14443-3 Description REQA and ATQA are implemented fully according to ISOIEC 14443-3 WUPA is implemented fully according to ISOIEC 14443-3 ANTICOLLISION and SELECT commands are implemented fully according to ISOIEC 14443-3 the response is part 1 of the UID ANTICOLLISION and SELECT commands are implemented fully according to ISOIEC 14443-3 the response is part 2 of the UID brings MIFARE DESFire EV1 to the HALT state ANTICOLLISIONSELECT Cascade Level 2

ISOIEC 14443-4
Table 5. Command RATS PPS ISOIEC 14443-4 Description identifies the MIFARE DESFire EV1 type to the PCD allows individual selection of the communication baud rate between PCD and MIFARE DESFire EV1 for DESFire it is possible to set different communication baud rates for each direction i.e. DESFire allows a non-symmetrical information interchange speed. if the MIFARE DESFire EV1 needs more time than the defined FWT to respond to a PCD command it requests a Waiting Time eXtension (WTX) allows MIFARE DESFire EV1 to be brought to the HALT state WTX DESELECT

MF3ICD21, MF3ICD41, MF3ICD81
MIFARE DESFire EV1 contactless multi-application IC, Table 6. Command Authenticate Security related commands Description MIFARE DESFire EV1 and the reader device show in an encrypted way that they possess the same secret which especially means the same key this not only confirms that both entities are permitted to perform operations on each other but also creates a session key which can be used to keep the further communication path secure as the name “session key” implicitly indicates, each time a new authentication procedure is successfully completed a new key for further cryptographic operations is generated changes the master key settings on MIFARE DESFire EV1 and application level configures the card and pre-personalizes the card with a key, defines if the UID or the random ID is sent back during communication setup and configures the ATS string changes any key stored on the MIFARE DESFire EV1 reads out the current key version of any key stored on the MIFARE DESFire EV1 Change KeySettings Set Configuration Change Key Get Key Version Remark: All command and data frames are exchanged between MIFARE DESFire EV1 and PCD by using block format as defined in ISOIEC 14443-4.

Table 7. Command Create Application Delete Application Get Applications IDs Free Memory GetDFNames Get KeySettings Level commands Description creates new applications on the MIFARE DESFire EV1 permanently deactivates applications on the MIFARE DESFire EV1 returns the Application IDentifiers of all applications on a MIFARE DESFire EV1 returns the free memory available on the card returns the DF names gets information on the MIFARE DESFire EV1 and application master key settings in addition it returns the maximum number of keys which are configured for the selected application selects one specific application for further access releases the MF3ICD81 user memory returns manufacturing related data of the MIFARE DESFire EV1 returns the UID Select Application FormatMF3ICD81 Get Version GetCardUID Remark: All command and data frames are exchanged between MIFARE DESFire EV1 and PCD by using block format as defined in ISOIEC 14443-4.

MF3ICD21, MF3ICD41, MF3ICD81
MIFARE DESFire EV1 contactless multi-application IC ,Table 8. Command Get FileIDs Get FileSettings Change FileSettings Create StdDataFile Create BackupDataFile Create ValueFile Create LinearRecordFile Application level commands Description returns the File IDentifiers of all active files within the currently selected application gets information on the properties of a specific file changes the access parameters of an existing file creates files for the storage of plain unformatted user data within an existing application on the MIFARE DESFire EV1 creates files for the storage of plain unformatted user data within an existing application on the MIFARE DESFire EV1, additionally supporting the feature of an integrated backup mechanism creates files for the storage and manipulation of 32-bit signed integer values within an existing application on the MIFARE DESFire EV1 creates files for multiple storage of similar structural data, for example, loyalty programs within an existing application on the MIFARE DESFire EV1 once the file is filled completely with data records, further writing to the file is not possible unless it is cleared creates files for multiple storage of similar structural data, for example, logging transactions within an existing application on the MIFARE DESFire EV1 once the file is filled completely with data records, the MIFARE DESFire EV1 automatically overwrites the oldest record with the latest written one (this wrap is fully transparent for the PCD) permanently deactivates a file within the file directory of the currently selected application Create CyclicRecordFile DeleteFile
Remark: All command and data frames are exchanged between MIFARE DESFire EV1 and PCD by using block format as defined in ISOIEC 14443-4.

Table 9. Command Read Data Write Data Get Value Credit Debit Limited Credit Write Record Read Records Data manipulation commands Description reads data from Standard Data files or Backup Data files writes data to Standard Data files or Backup Data files reads the currently stored value from Value files increases a value stored in a Value file decreases a value stored in a Value file allows a limited increase of a value stored in a Value file without having full Credit permissions to the file writes data to a record in a Cyclic or Linear Record file reads out a set of complete records from a Cyclic or Linear Record file.

MF3ICD21, MF3ICD41, MF3ICD81
MIFARE DESFire EV1 contactless multi-application IC

1. General description
MIFARE DESFire EV1 is ideal for service providers wanting to use multi-application smart cards in transport schemes, eGovernment or identity applications. It fully complies with the requirements for fast and highly secure data transmission, flexible memory organization and interoperability with existing infrastructure. MIFARE DESFire EV1 is based on open global standards for both air interface and cryptographic methods. It is compliant to all 4 levels of ISOIEC 14443A and uses optional ISOIEC 7816-4 commands. Featuring an on-chip backup management system and the mutual three pass authentication, a MIFARE DESFire EV1 card can hold up to 28 different applications and 32 files per application. The size of each file is defined at the moment of its creation, making MIFARE DESFire EV1 a truly flexible and convenient product. Additionally, an automatic anti-tear mechanism is available for all file types, which guarantees transaction oriented data integrity. With MIFARE DESFire EV1, data transfer rates up to 848 kbits can be achieved, allowing fast data transmission. The main characteristics of this device are denoted by its name DESFire EV1: DES indicates the high level of security using a 3DES hardware cryptographic engine for enciphering transmission data and Fire indicates its outstanding position as a fast, innovative, reliable and secure IC in the contactless proximity transaction market. Hence, MIFARE DESFire EV1 brings many benefits to end users. Cardholders can experience convenient contactless ticketing while also having the possibility to use the same device for related applications such as payment at vending machines, access control or event ticketing. In other words, the MIFARE DESFire EV1 silicon solution offers enhanced consumer-friendly system design, in combination with security and reliability. MIFARE DESFire EV1 delivers the perfect balance of speed, performance and cost efficiency. Its open concept allows future seamless integration of other ticketing media such as smart paper tickets, key fobs, and mobile ticketing based on Near Field Communication (NFC) technology. It is also fully compatible with the existing MIFARE reader hardware platform. MIFARE DESFire EV1 is your ticket to contactless systems worldwide.

MF3ICD21, MF3ICD41, MF3ICD81
MIFARE DESFire EV1 contactless multi-application IC
2. Features
2.1 Key features

3. Applications
I I I I I Advanced public transportation High secure access control Event ticketing eGovernment Identity
2 KB and 4 KB versions are also available.

MF3ICD21, MF3ICD41, MF3ICD81
MIFARE DESFire EV1 contactless multi-application IC
4. Quick reference data
Conditions
Min 14.96
Typ 13.56 17.0
Max 19.04
Unit MHz pF
EEPROM characteristics tret Nendu(W) tcy(W)
retention time write endurance write cycle time
year cycle ms
Stresses above one or more of the values may cause permanent damage to the device. Exposure to limiting values for extended periods may affect device reliability. Measured with LCR meter.
5. Ordering information

1 This package is also known as MOA4.
Type number
Version -
SOT500-2 SOT500-2 SOT500-2

MF3ICD21, MF3ICD41, MF3ICD81
MIFARE DESFire EV1 contactless multi-application IC
6. Block diagram
RF INTERFACE SECURITY SENSORS POWER ON RESET VOLTAGE REGULATOR CLOCK INPUT FILTER RESET GENERATOR
UART ISOIEC 14443A
CRYPTO CO-PROCESSOR
TRUE RANDOM NUMBER GENERATOR
EEPROM
001aah878
Fig 1.
Block diagram of MF3ICD81, MF3ICD41, MF3ICD21
7. Limiting values
Table 3. Limiting values 12 In accordance with the Absolute Maximum Rating System (IEC 60134). Symbol II Ptotpack Tstg Tamb VESD Ilu
Parameter input current total power dissipation per package storage temperature ambient temperature electrostatic discharge voltage latch-up current
Conditions
Min -55 -25
Max 30 200 125 70 -
MF3ICD21, MF3ICD41, MF3ICD81
MIFARE DESFire EV1 contactless multi-application IC
8. Functional description
8.1 Contactless energy and data transfer
In the MIFARE system, the MIFARE DESFire EV1 is connected to a coil consisting of a few turns embedded in a standard ISOIEC smart card (see Ref. 7). 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 kbits.
8.2 Anti-collision
An intelligent anti-collision mechanism allows more than one MIFARE DESFire EV1 in the field to be handled simultaneously. The anti-collision algorithm selects each MIFARE DESFire EV1 individually and ensures that the execution of a transaction with a selected MIFARE DESFire EV1 is performed correctly without data corruption resulting from other MIFARE DESFire EV1s in the field.
8.3 UIDserial 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 ISOIEC 14443-3 (see Ref. 11) 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. SN0 holds the manufacturer ID for NXP (04h) according to ISOIEC 14443-3 and ISOIEC 7816-6 AMD 1. MIFARE DESFire EV1 also allows Random ID to be used. In this case MIFARE DESFire EV1 only uses a single anti-collision loop. The 3 byte random number is generated after RF reset of the MIFARE DESFire EV1.
8.4 Memory organization
The 248 KB NV memory is organized using a flexible file system. This file system allows a maximum of 28 different applications on one MIFARE DESFire EV1. Each application provides up to 32 files. Every application is represented by its 3 bytes Application IDentifier (AID). Five different file types are supported see Section 8.5. A guideline to assign DESFire AIDs can be found in the application note MIFARE Application Directory (MAD) see Ref. 8. Each file can be created either at MIFARE DESFire EV1 initialization (card productioncard printing), at MIFARE DESFire EV1 personalization (vending machine) or in the field. If a file or application becomes obsolete in operation, it can be permanently invalidated. Commands which have impact on the file structure itself (e.g. creation or deletion of applications, change of keys) activate an automatic rollback mechanism, which protects the file structure from being corrupted.