Results returned by BlackBerry NFC API Target.geturi (target.iso_14443_3)

Tested, each card can only respond correctly to one type of connection.

The test results are as follows:

==============================================================================

Mifare Ultralight (Hua Hong) BlackBerry API Target.geturi (target.iso_14443_3) results returned:

nfc:raw:33554556

can establish iso14443part3connection connection, send 0x30 read instruction to read data
==============================================================================

Mifare 1K (Hua Hong, Taobao), Mifare 4K (Beijing Taobao): BlackBerry API Target.geturi (target.iso_14443_3) results returned:

nfc:raw:33554556

can establish iso14443part3connection connection, but send 0x30 read instruction error error exchaning iso14443-3 data:unexpected error
==============================================================================
DESFire 4K (Beijing Taobao):
Results returned by the BlackBerry API Target.geturi (target.iso_14443_4):

nfc:iso14443:33554473

can establish a iso14443part4connection connection, but send 0x30 read instruction or 0x60 authentication command after the return result is always two byte-9700, it seems that desfire do not recognize the two directives.
==============================================================================
Mifare Ultralight empty card/card with smart tag:
BlackBerry API Target.geturi (T arget. Ndef_tag) Returns the result:
nfc:ndef:33554502

Unable to establish connection (null connection)

==============================================================================

Reference:

Description of the target class:

Represents a card or tag that the NFC controller detected. Also identifies the type of contactless protocol that's used to connect to the card or tag. Contactless protocols is grouped into four categories (beginning with the lowest layer): Iso_14443_3 covers ISO 14443, A- 3, B-3 Iso_14443_4 covers ISO 14443, A-4, B-4 Ndef_tag covers NFC tags type 1, 2, 3, 4