NFC Device Interoperability Test Scenarios

This documentation proposes interoperability test scenarios for NFC Devices such as smartphones, tablets, laptops and other comparably capable computing devices. NFC Devices that would typically be characterized as embedded or functionally restricted devices are not subject of the proposal.

All interoperability test scenarios are intended to be run by a Device In Testmode against a Device Under Test and for any given pairing of Device A and Device B to be executed once with Device A as the Device In Testmode and Device B as the Device Under Test, and once with Device A as the Device Under Test and Device B as the Device In Testmode.

List of Interoperability Test Requirements

Peer Communication

  • The interoperability test scenarios require that NFC devices implement at least LLCP Version 1.1. (ref)
  • The interoperability test scenarios require that NFC devices have a Link MIU of 248 octets or more. (ref)
  • The interoperability test scenarios require that NFC devices send a WKS parameter during link activation. (ref)
  • The interoperability test scenarios require that if an LTO parameter then the resulting remote Link Timeout value does not exceed 1000 milliseconds. (ref)
  • The interoperability test scenarios require that NFC devices support both connection-less and connection-oriented transport type and send an an OPT parameter during link activation. (ref)
  • The interoperability test scenarios require that NFC devices send a SYMM PDU no later than 10 milliseconds after a PDU was received and no other PDU became availble for sending. (ref)
  • The interoperability test scenarios require that NFC devices do not increase the time between receiving and sending a SYMM PDU before at least a consecutive sequence of 10 SYMM PDUs has been received and send (5 per direction). (ref)
  • The interoperability test scenarios require that NFC devices implement and use frame aggregation. (ref)

Small Data Exchange

  • The interoperability test scenarios require that a Default SNEP Server implementation either dispatches or makes visible the NDEF message received such that the success of receiving can be clearly identified. (ref)
  • The interoperability test scenarios require that a Default SNEP Server implementation supports NDEF message sizes of at least 20480 byte (20 KByte). (ref)
  • The interoperability test scenarios require that a Default SNEP Server implementation supports a data link connection receive window of 2 or more and a maximum information unit size of 1984 octets. (ref)

Connection Handover

  • The interoperability test scenarios require that Bluetooth BR/EDR Carrier Configuration data includes the Simple Pairing Hash and Randomizer if negotiated handover is performed. (ref)
  • The interoperability test scenarios require that Bluetooth BR/EDR Carrier Configuration data includes the Bluetooth Local Name (Device Name). (ref)
  • The interoperability test scenarios require that Bluetooth LE Carrier Configuration data includes the Temporary Key TK value if negotiated handover is performed. (ref)
  • The interoperability test scenarios require that Bluetooth LE Carrier Configuration data includes the Bluetooth Local Name (Bluetooth Device Name). (ref)
  • The interoperability test scenarios require that a connection handover implementation provides a data link connection MIU of at least 248 octets. (ref)
  • The interoperability test scenarios require that an NFC Device with alternative carrier technologies such as Bluetooth or Wi-Fi implements the NFC Forum Connection Handover specification. (ref)

License

This work is licensed under the Creative Commons Attribution 4.0 International License.