Specifications

1.19 NFC(Near Field Communication)

The following types of smart card can be accessed for reading and writing by the Near Field

Communication (hereafter referred to it as NFC) integrated in the terminal.

• ISO/IEC14443 Type A (MIFARE Standard; Ultralight) See note 1.

• ISO/IEC14443 Type B

• FeliCa See note2.

• ISO15693(ICODE SLI, ICODE SLI-L, ICODE SLI-S, my-d V 10 Plain, my-d Light, Tag-it HF-I

Plus, Tag-it HF-I Pro, Tag-it HF-I Standard) See note 3.

Notes

1. Verification is required at the time of installation, because some cards may not follow ISO

standard.

2. The FeliCa security area can be accessed by using a FeliCa SAM card “RC-S251”.

RC-S251 can be accessed from the SAM library.

3. About Tag-it series, Lock AFI / LockDSFID command is not supported by NFC

controller specification. And it takes time to write data of Tag-it. Some commands are

required on the application verification process.

The functions of the android API related with the “NFC“ are as shown below.

android.nfc

: The class that provides access to Near Field Communication (NFC) functionality.

Tag-it Control

Please note in case you develop a software that executes Tag-it command on Android 4.0.

If following Tag-it commands are executed by "android.nfc.tech.NfcV.transceive" method,

IOException will occur even if the result is success.

For that reason, when you develop a software that executes these Tag-it commands, please use

try-catch block that executes Tag-it command in the try block and verify the result in the catch

block.

Table 2.16 Tag-it commands

Tag-it command How to verify

Write Single Block Retrieve data by "Read Single Block" and compare.

Lock Block Check whether the locked by "Read Single Block".

Write AFI Check the AFI by “Get System Information”.

Write DSFID Check the DSFID by “Get System Information”.

Please perform retry processing from a command again without considering it as an error

immediately, even when the result of a check is unusual.

Since write-in processing of Tag-it may be set to about 250 msec, as for the number of times of a

retry, 1 to 5 times becomes a standard.

Please keep in mind that there is a possibility that the response at the time of an error may exceed

1 second when it is made more.