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

8 / 33

8.2 Virtual Card Architecture

One of the trends expected is that mobile phones and other personal devices are used

for making contactless transactions, in addition to the usage of traditional contactless

cards (PICCs).

In the case of mobile phones used for contactless operation, there needs to be multi-

application functionality of unrelated service providers and unrelated "Card Issuers" and

a single mobile phone should work with multiple infrastructures. However, this multi-

application functionality is to be such that it is transparent to the various installations and

that the mobile phone can be accessed like a normal contactless card.

With the implemented Virtual Cards (VCs) concept, a Proximity Device (PD), e.g. the

Secure Element in a mobile phone, can hold multiple VCs. With having multiple VCs in a

single device there are several requirements:

1. It must be determined how the appropriate VC to use gets selected, in other words

how a specific VC is to be presented at a given moment.

2. Privacy considerations need to be maintained. When a device can be freely

interrogated about its UID, VC specific information (like implementation, file layout, ...)

or even only to what installations the supported VCs belong, this data or the

combination of a subset of it would make it possible to track a person from location to

location. Furthermore, the combination of VCs could reveal a category of persons.

3. Performance and ease of use. The selection of the appropriate VC must be done fast,

in order to increase transaction times only minimally.

4. Compliancy and portability to existing Card OSes supporting application selection

methods on secure chip technologies, as defined by Java Card and GlobalPlatform.

The Virtual Card Architecture as implemented on the MF1P(H)x1y1 has the following

benefits:

• Fast VC selection is possible by issuing a single ISOSelect command as defined by

ISO/IEC 7816-4

• If Random ID is used, the UID can be retrieved in a very fast and secure way from the

VC using ISOSelect and ISOExternalAuthenticate

• Detect whether a VC belongs to certain installation and do so fast and privacy friendly

• Proximity Check may also be enforced via a configuration, giving additionally protection

against relay attacks

• Exchange capabilities, e.g. a key-set version indication together with the fast retrieval

of the UID.