OOB over NFC message content

[Alex]

Can anyone please provide content of m_ndef_msg_buf and ndef_msg_len as a result of nfc_ble_pair_default_msg_encode() running in debug mode? Or can Nordic provide structure of that record? Basically I'm using external NFC tag with nRF51 and want to implement OOB with Android 7. I'm using my own record which includes pairing LE type message and it works fine for non-OOB type of pairing. I don't have nRF52 boards to check examples from this blog but I can see that example has record with not only LE but EP type and both of them have different information inside. It is difficult to do reverse engineering of the code. Thanks in advance.

[bjorn-spockeli]

Hi Alex, you can find detailed information and examples for the content in the LE and EPOOB records in the Bluetooth Secure Simple Pairing Using NFC Application Document created by NFC Forum, it can be downloaded using this link.

We recommend that you use a simplified format (i.e. NFC_BLE_PAIR_MSG_BLUETOOTH_LE_SHORT, which corresponds to the nfc_ble_simplified_le_oob_msg_encode function and the example shown in section 4.3.2 in the Bluetooth Secure Simple Pairing Using NFC Application Document.

Best regards

Bjørn

[Alex]

Hi, thank you, it works, at least with Android. I did use originally short format. Found that all data types for LE and EP records are defined in ble_gap.h as BLE_GAP_AD_TYPE_xxxx