Home
Главная
Xiaomi
Смартфон
Redmi Note 8 64Gb+4Gb Dual LTE
Руководство по эксплуатации Страница: 99

Xiaomi Redmi Note 8 64Gb+4Gb Dual LTE Руководство по эксплуатации онлайн [99/132] 774794

enabled or another proprietary NFC P2p mode is turned on.

[C-1-6] 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.

[C-1-7] MUST honor the android.settings.NFCSHARING_SETTINGS intent to show NFC sharing

settings .

[C-1-8] MUST implement the NPP server. Messages received by the NPP server MUST be

processed the same way as the SNEP default server.

[C-1-9] 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.

[C-1-10] 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.

[C-1-11] MUST support NFC Connection handover to Bluetooth when the device supports

Bluetooth Object Push Profile.

[C-1-12] MUST support connection handover to Bluetooth when using

android.nfc.NfcAdapter.setBeamPushUris , by implementing the “ Connection Handover version

1.2 ” and “ Bluetooth Secure Simple Pairing Using NFC version 1.0 ” 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.

[C-1-13] 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.

SHOULD be capable of reading the barcode and URL (if encoded) of Thinfilm NFC Barcode

products.

Note that publicly available links are not available for the JIS, ISO, and NFC Forum specifications

cited above.

Android includes support for NFC Host Card Emulation (HCE) mode.

If device implementations include an NFC controller chipset capable of HCE (for NfcA and/or NfcB)

and support Application ID (AID) routing, they:

[C-2-1] MUST report the android.hardware.nfc.hce feature constant.

[C-2-2] MUST support NFC HCE APIs as defined in the Android SDK.

If device implementations include an NFC controller chipset capable of HCE for NfcF, and implement

the feature for third-party applications, they:

[C-3-1] MUST report the android.hardware.nfc.hcef feature constant.

[C-3-2] MUST implement the NfcF Card Emulation APIs as defined in the Android SDK.

If device implementations include general NFC support as described in this section and support

MIFARE technologies (MIFARE Classic, MIFARE Ultralight, NDEF on MIFARE Classic) in the

Page 99 of 132

Xiaomi Redmi Note 8 64Gb+4Gb Dual LTE Руководство по эксплуатации онлайн [99/132] 774794

Содержание

Похожие устройства