IT. Expert System.

Android Reference

MifareUltralight


android.nfc.tech

Class MifareUltralight

  • All Implemented Interfaces:
    TagTechnology, Closeable, AutoCloseable


    public final class MifareUltralight
    extends Object
    Provides access to MIFARE Ultralight properties and I/O operations on a Tag.

    Acquire a MifareUltralight object using get(android.nfc.Tag).

    MIFARE Ultralight compatible tags have 4 byte pages PAGE_SIZE. The primary operations on an Ultralight tag are readPages(int) and writePage(int, byte[]).

    The original MIFARE Ultralight consists of a 64 byte EEPROM. The first 4 pages are for the OTP area, manufacturer data, and locking bits. They are readable and some bits are writable. The final 12 pages are the user read/write area. For more information see the NXP data sheet MF0ICU1.

    The MIFARE Ultralight C consists of a 192 byte EEPROM. The first 4 pages are for OTP, manufacturer data, and locking bits. The next 36 pages are the user read/write area. The next 4 pages are additional locking bits, counters and authentication configuration and are readable. The final 4 pages are for the authentication key and are not readable. For more information see the NXP data sheet MF0ICU2.

    Implementation of this class on a Android NFC device is optional. If it is not implemented, then MifareUltralight will never be enumerated in Tag.getTechList(). If it is enumerated, then all MifareUltralight I/O operations will be supported. In either case, NfcA will also be enumerated on the tag, because all MIFARE Ultralight tags are also NfcA tags.

    Note: Methods that perform I/O operations require the android.Manifest.permission#NFC permission.

    • Method Detail

      • get

        public static MifareUltralight get(Tag tag)
        Get an instance of MifareUltralight for the given tag.

        Returns null if MifareUltralight was not enumerated in Tag.getTechList() - this indicates the tag is not MIFARE Ultralight compatible, or that this Android device does not implement MIFARE Ultralight.

        Does not cause any RF activity and does not block.

        Parameters:
        tag - an MIFARE Ultralight compatible tag
        Returns:
        MIFARE Ultralight object
      • getType

        public int getType()
        Return the MIFARE Ultralight type of the tag.

        One of TYPE_ULTRALIGHT or TYPE_ULTRALIGHT_C or TYPE_UNKNOWN.

        Depending on how the tag has been formatted, it can be impossible to accurately classify between original MIFARE Ultralight and Ultralight C. So treat this method as a hint.

        Does not cause any RF activity and does not block.

        Returns:
        the type
      • readPages

        public byte[] readPages(int pageOffset)
                         throws IOException
        Read 4 pages (16 bytes).

        The MIFARE Ultralight protocol always reads 4 pages at a time, to reduce the number of commands required to read an entire tag.

        If a read spans past the last readable block, then the tag will return pages that have been wrapped back to the first blocks. MIFARE Ultralight tags have readable blocks 0x00 through 0x0F. So a read to block offset 0x0E would return blocks 0x0E, 0x0F, 0x00, 0x01. MIFARE Ultralight C tags have readable blocks 0x00 through 0x2B. So a read to block 0x2A would return blocks 0x2A, 0x2B, 0x00, 0x01.

        This is an I/O operation and will block until complete. It must not be called from the main application thread. A blocked call will be canceled with IOException if close() is called from another thread.

        Requires the android.Manifest.permission#NFC permission.

        Parameters:
        pageOffset - index of first page to read, starting from 0
        Returns:
        4 pages (16 bytes)
        Throws:
        TagLostException - if the tag leaves the field
        IOException - if there is an I/O failure, or the operation is canceled
      • writePage

        public void writePage(int pageOffset,
                     byte[] data)
                       throws IOException
        Write 1 page (4 bytes).

        The MIFARE Ultralight protocol always writes 1 page at a time, to minimize EEPROM write cycles.

        This is an I/O operation and will block until complete. It must not be called from the main application thread. A blocked call will be canceled with IOException if close() is called from another thread.

        Requires the android.Manifest.permission#NFC permission.

        Parameters:
        pageOffset - index of page to write, starting from 0
        data - 4 bytes to write
        Throws:
        TagLostException - if the tag leaves the field
        IOException - if there is an I/O failure, or the operation is canceled
      • transceive

        public byte[] transceive(byte[] data)
                          throws IOException
        Send raw NfcA data to a tag and receive the response.

        This is equivalent to connecting to this tag via NfcA and calling NfcA.transceive(byte[]). Note that all MIFARE Classic tags are based on NfcA technology.

        Use getMaxTransceiveLength() to retrieve the maximum number of bytes that can be sent with transceive(byte[]).

        This is an I/O operation and will block until complete. It must not be called from the main application thread. A blocked call will be canceled with IOException if close() is called from another thread.

        Requires the android.Manifest.permission#NFC permission.

        Throws:
        IOException
        See Also:
        NfcA.transceive(byte[])
      • getMaxTransceiveLength

        public int getMaxTransceiveLength()
        Return the maximum number of bytes that can be sent with transceive(byte[]).
        Returns:
        the maximum number of bytes that can be sent with transceive(byte[]).
      • setTimeout

        public void setTimeout(int timeout)
        Set the transceive(byte[]) timeout in milliseconds.

        The timeout only applies to transceive(byte[]) on this object, and is reset to a default value when close() is called.

        Setting a longer timeout may be useful when performing transactions that require a long processing time on the tag such as key generation.

        Requires the android.Manifest.permission#NFC permission.

        Parameters:
        timeout - timeout value in milliseconds
      • getTimeout

        public int getTimeout()
        Get the current transceive(byte[]) timeout in milliseconds.

        Requires the android.Manifest.permission#NFC permission.

        Returns:
        timeout value in milliseconds
      • isConnected

        public boolean isConnected()
        Description copied from interface: TagTechnology
        Helper to indicate if I/O operations should be possible.

        Returns true if TagTechnology.connect() has completed, and TagTechnology.close() has not been called, and the Tag is not known to be out of range.

        Does not cause RF activity, and does not block.

        Specified by:
        isConnected in interface TagTechnology
        Returns:
        true if I/O operations should be possible


Content

Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)

SQL

HTML

PHP

CSS

Java Script

MYSQL

JQUERY

VBS

REGEX

C

C++

C#

Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

License.
All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 128 / 158681236. Delta: 0.14943 с