NXP Semiconductors

MF1P(H)x1y1

MIFARE Plus EV1

MF1P(H)x1y1

All information provided in this document is subject to legal disclaimers.

© NXP B.V. 2019. All rights reserved.

Product short data sheet

Rev. 3.2 — 6 December 2018

COMPANY PUBLIC

366932

7 / 33

Value blocks are special counters where the stored value can be manipulated with

specific commands such as Increment, Decrement and Transfer.

These value blocks have a fixed data format enabling error detection and correction with

backup management to be performed.

The MIFARE Plus EV1 in security level 3 provides two more commands which can be

used to optimize performance when using value blocks. These are:

• IncrementTransfer

• DecrementTransfer

A successful mutual authentication is required to allow any data operation.

8.1.2.1 Access conditions

The access conditions for every data block and the sector trailer itself are stored in the

sector trailer of the corresponding sector.

The access bits control the rights of memory operations using the secret keys A and B.

The access conditions may be altered after authentication with the relevant key and the

current access condition allows this operation.

Furthermore, value blocks are configured using the access bits.

8.1.3 AES keys

AES keys are not shown in the memory map. The keys are stored in a separate memory

section and can be updated and used by referencing the Key Number. Updates of AES

keys as well as the update of the sector trailers is protected against tearing events. This

anti-tearing mechanism is done by the PICC itself. The EEPROM stays in a defined

status, even if the PICC is removed from the electromagnetic field during the write

operation.

8.1.4 Originality function

MIFARE Plus EV1 offers two features to prove genuineness of the IC. The first originality

function is implemented by an AES authentication with the originality key and is

backwards compatible to MIFARE Plus EV0. The authentication is performed in ISO/IEC

14443-4 protocol layer.

The second asymmetric originality signature is based on ECC and only requires a public

key for the verification. The verification itself is done on the infrastructure side.