Android HCE does not have any means to set these values. Some readers may require certain parameter values in lower protocol layers (such as a specific UID cascade-level, a certain ATQA value, a certain SAK value, or a certain ATS). Thus, it may be possible to emulate this protocol using Android HCE.
#MIFARE CARD EMULATION ON ANDROID ISO#
ISO protocol: This protocol is based on ISO/IEC 7816-4 and uses application selection by AID.(Note: Newer reader implementations are more likely to issue a SELECT command that is compatible with Android HCE as this is also required for some of NXP’s newer smartcard products with DESFire protocol emulation.) wrapped native protocol: This protocol uses APDUs according to ISO/IEC 7816-4, however, readers will typically not issue a SELECT command using the DESFire AID when starting to communicate with a card in wrapped native command mode.native protocol: As this protocol does not use APDUs according to ISO/IEC 7816-4 its not possible to emulate it using Android HCE.There are three variants of the DESFire protocol: MIFARE DESFire protocols operate on top of ISO/IEC 14443-4. Thus, its also not possible to emulate MIFARE Classic using Android HCE.
MIFARE Classic protocol partially operates on top of ISO/IEC 14443-3 (with some different framing).It is not possible to emulate cards using such low layer protocols using Android HCE. MIFARE Ultralight (and derivates) protocol operates on top of ISO/IEC 14443-3.So regarding emulation of various MIFARE protocols: Moreover, the API doesn’t give you any means to specify if card emulation should be done using Type A or Type B protocol. More specifically you can only emulate application structures according to ISO/IEC 7816-4 (thus card emulation applications need to be selected though an AID). With host-based card emulation (HCE) in Android 4.4 you can only emulate the ISO/IEC 14443-4 protocol.
0 kommentar(er)
