Compatibility Definition

SHOULD be capable of reading the barcode and URL (if encoded) of Thinfilm
NFC Barcode [Resources, 102] products.
MUST be capable of transmitting and receiving data via the following peer-topeer
standards and protocols:
ISO 18092
LLCP 1.2 (defined by the NFC Forum)
SDP 1.0 (defined by the NFC Forum)
NDEF Push Protocol [Resources, 103]
SNEP 1.0 (defined by the NFC Forum)
MUST include support for Android Beam [Resources, 104]:
MUST implement the SNEP default server. Valid NDEF messages
received by the default SNEP server MUST be dispatched to
applications using the android.nfc.ACTION_NDEF_DISCOVERED
intent. Disabling Android Beam in settings MUST NOT disable
dispatch of incoming NDEF message.
MUST honor the android.settings.NFCSHARING_SETTINGS intent
to show NFC sharing settings [Resources, 105].
MUST implement the NPP server. Messages received by the NPP
server MUST be processed the same way as the SNEP default
server.
MUST implement a SNEP client and attempt to send outbound P2P
NDEF to the default SNEP server when Android Beam is enabled. If
no default SNEP server is found then the client MUST attempt to
send to an NPP server.
MUST allow foreground activities to set the outbound P2P NDEF
message using android.nfc.NfcAdapter.setNdefPushMessage, and
android.nfc.NfcAdapter.setNdefPushMessageCallback, and
android.nfc.NfcAdapter.enableForegroundNdefPush.
SHOULD use a gesture or on-screen confirmation, such as 'Touch
to Beam', before sending outbound P2P NDEF messages.
SHOULD enable Android Beam by default and MUST be able to
send and receive using Android Beam, even when another
proprietary NFC P2p mode is turned on.
MUST support NFC Connection handover to Bluetooth when the
device supports Bluetooth Object Push Profile. Device
implementations MUST support connection handover to Bluetooth
when using android.nfc.NfcAdapter.setBeamPushUris, by
implementing the “Connection Handover version 1.2” [Resources,
106] and “Bluetooth Secure Simple Pairing Using NFC version 1.0”
[Resources, 107] specs from the NFC Forum. Such an
implementation MUST implement the handover LLCP service with
service name “urn:nfc:sn:handover” for exchanging the handover
request/select records over NFC, and it MUST use the Bluetooth
Object Push Profile for the actual Bluetooth data transfer. For
legacy reasons (to remain compatible with Android 4.1 devices), the
implementation SHOULD still accept SNEP GET requests for
exchanging the handover request/select records over NFC.
However an implementation itself SHOULD NOT send SNEP GET
requests for performing connection handover.
MUST poll for all supported technologies while in NFC discovery mode.
SHOULD be in NFC discovery mode while the device is awake with the screen
active and the lock-screen unlocked.
Page 51 of 74