I would like to pass through the LLCP the user data in the NDEF message in one NDEF record (or maybe the payload will be split into several NDEF records). Transported content is a file with a specific format that matters only in a particular application. So what is the best approach for specifying an NDEF header?
1) Set TNF to 0x04 (external NFC Forum type), 0x03 (absolute URI) or 0x05 (unknown)? 0x04 will have a user relative URI of the TYPE field in the case of an absolute URI of 0x03. 0x05 I do not really like it, because the receiving device cannot identify the data processing application, because TYPE should be empty in this case (only the ID field can help here).
2) The ID field is intended for the uniqueness of the NDEF message, so it can be either empty or contain a user identifier in the form, for example. com.company.nfc.application_name&id=message_generated_uuid
My opinion is the use of TNF 0x03 or 0x04 is the preferred way, leaving the identifier blank if the messages do not need additional identification, which would be better to transfer beyond the payload.
BR sten
source
share